Students

ISYS254 – Applications Modelling and Development

2018 – S1 Day

General Information

Download as PDF
Unit convenor and teaching staff Unit convenor and teaching staff Convenor and Lecturer
Charanya Ramakrishnan
2nd year lab - during consultation times
Lecturer
Stephen Smith
Contact via Email
E6A Room Number: 381
1hr prior to Lectures in office
Tutor
Carl Svensson
2nd year lab - during consultation times
Tutor
Hedieh Ranjbartabar
2nd year lab - during consultation times
Tutor
Natalie Batshon
2nd year lab - during consultation times
Tutor
Farshid Anvari
2nd year lab - during consultation times
Credit points Credit points
3
Prerequisites Prerequisites
ISYS114
Corequisites Corequisites
Co-badged status Co-badged status
ITEC654
Unit description Unit description
This unit is an intermediate unit to deliver a solid foundation in concepts, methods, tools and techniques that organisations use to control the information they use in their day-to-day business, with a particular focus on how computer-based technologies can most effectively contribute to the way business is structured. The units focuses on the fundamental concepts and models of applications development so that they can understand the key processes related to building functioning applications and appreciate the complexity of applications development. The unit emphasises program development and incorporates the software development life cycle, requirements gathering, designing a solution, and implementing and testing a solution in a programming language.

Important Academic Dates

Information about important academic dates including deadlines for withdrawing from units are available at https://www.mq.edu.au/study/calendar-of-dates

Learning Outcomes

On successful completion of this unit, you will be able to:

  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

General Assessment Information

If you receive special consideration for the final exam, a supplementary exam will be scheduled in the interval between the regular exam period and the start of the next session.  By making a special consideration application for the final exam you are declaring yourself available for a resit during the supplementary examination period and will not be eligible for a second special consideration approval based on pre-existing commitments.  Please ensure you are familiar with the policy prior to submitting an application. You can check the supplementary exam information page on FSE101 in iLearn (bit.ly/FSESupp) for dates, and approved applicants will receive an individual notification one week prior to the exam with the exact date and time of their supplementary examination.

Assessment Tasks

Name Weighting Hurdle Due
Workshop Participation 10% No Weekly
Evaluating Conceptual Design 5% No to be changed-draft
Requirements and Modelling 15% No Friday Apr 13, Wk7, 11.55pm
App. Dev. Proj - Design 10% No Friday May 11, Wk9, 11.55pm
App. Dev. Proj - Development 15% No Friday June 1, Wk 12 11.55pm
Final Examination 45% No TBA

Workshop Participation

Due: Weekly
Weighting: 10%

Workshops are combined practicals and tutorials. Workshops will involve a range of activities, some individual, some in pairs, some in groups. Be prepared to present your ideas. 

Workshops are the key learning activity in this unit and your weekly attendance and active participation is expected. Each week your attendance will be recorded in your scheduled workshop and you will receive 1 mark for attendance & active participation. There are 12 weeks of workshops, however, the total attendance mark is limited to 10 throughout the semester. 

​Attendance at workshops in this unit is NOT a hurdle requirement. However, if you do not attend all the workshops, you are unlikely to have sufficient knowledge to pass the exam or sufficient total marks to be able to pass the unit. 


On successful completion you will be able to:
  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Evaluating Conceptual Design

Due: to be changed-draft
Weighting: 5%

You will use a rubric to evaluate the conceptual design of your peers. The designs will be captured in workshops in Week 6. 

The details of the rubric and how to access the design will be provided on iLearn.


On successful completion you will be able to:
  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.

Requirements and Modelling

Due: Friday Apr 13, Wk7, 11.55pm
Weighting: 15%

This is an individual assignment which will develop and test your skills in requirements gathering, specification, analysis and modelling.

Assignment specification and submission via iLearn.


On successful completion you will be able to:
  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.

App. Dev. Proj - Design

Due: Friday May 11, Wk9, 11.55pm
Weighting: 10%

You will need to form into pairs. Use iLearn to put yourself into a group by the end of week 6. Instructions for doing this will be given in class and in the news forum.Assignment two will have two parts. The first part will assess your design and database skills. 

Assignment specification will be available on the iLearn site. Submission will be via iLearn.


On successful completion you will be able to:
  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

App. Dev. Proj - Development

Due: Friday June 1, Wk 12 11.55pm
Weighting: 15%

The second part of assignment 2 will assess your development skills. You will remain in the same group you had for part I

This assignment will be marked in Workshops in Week 13. Both people in the pair must be present to demonstrate their understanding of the application to receive the mark awarded.


On successful completion you will be able to:
  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Final Examination

Due: TBA
Weighting: 45%

Closed Examination

This closed book exam will test your knowledge of the concepts and ability to apply the learning material for Weeks 1-12.

 


On successful completion you will be able to:
  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Delivery and Resources

CLASSES

ISYS254 is taught via lectures and workshops.

Lectures:

  • Lectures are used to introduce new material, provide motivation and context for your study, guide you in what is important to learn and explain more difficult concepts.
  • There are 2 hours of lectures per week.
  • Lectures will be on Wednesday from 4pm to 6pm in 23 Wallys Wlk - P.G.Price Theatre

Workshops:

  • Workshops are small group classes which give you the opportunity to interact with your peers and with a tutor who has a sound knowledge of the subject. This also gives you a chance to practice your technology skills.
  • You will need to enrol and attend the workshop to obtain marks for your attendance and participation
  • Note: Workshops commence in Week-2
  • For details of days, times and rooms consult the timetables webpage.

REQUIRED AND RECOMMENDED TEXTS AND/OR MATERIALS

Textbook

The textbooks for ISYS254 used this semester is:

  1. Kenneth E. Kendall and Julie E Kendall.,Systems Analysis and Design, Ninth Edition, Pearson, 2012, ISBN13: 978-0-273-78710-5

Note: The book can be found at the co-op bookshop.

UNIT WEBPAGE AND TECHNOLOGY USED AND REQUIRED

Websites

The web page for this unit can be found at: here

iLecture

Digital recordings of lectures are available. Read instructions here.

Technology 

Power Designer, Node, Python2, JDK, React Native CLI, Atom, MS Word

Discussion Boards

The unit makes use of discussion boards hosted within ilearn Please post questions of general interest there (for example, about assessment tasks), they are monitored by the unit staff but students may also provide answers. 

FEEDBACK

You have many opportunities to seek for and to receive feedback. The feedback that you receive also plays an important role in your learning. Make sure you read the feedback you are given, attend lectures which provide assignment feedback and compare your solution with sample solutions provided. During lectures, you are encouraged to ask the lecturer questions to clarify anything you might not be sure of. You may also arrange to meet with your tutor or the lecturer or attend the consultation hours of any tutor. Each week, you will be given activities and problems to solve in the workshops. This will at times involve contributing to a group of students and presenting solutions to the class. The solutions provided will help you to understand the material in the unit, prepare you for the work in assignments as well as for the final exam. It is important that you keep up with these problems every week. Assignments have been especially designed to deliver continuous feedback on your work.

Each week you should:

  • Attend lectures, take notes, ask questions
  • Attend your tutorial/practical and seek feedback from your tutor on your work
  • Read assigned reading material (ideally before the lecture), add to your notes and prepare questions for your lecturer or tutor
  • Start working on any assignments immediately after they have been released. 

Lecture notes are made available each week but these notes are intended as an outline of the lecture only and are not a substitute for your own notes or reading of the textbook or other additional material.

Unit Schedule

Week Topic Reading Lecturer
1

Unit Overview + Development Methodologies + Information Gathering

Chp 1 & 4 Smith
2 O-O Analysis and Design: Information Gathering + Use Case Diagrams Chp 2, 5 and online resources Smith
3 O-O Analysis and Design: Using Data flow Diagrams, Class, Sequence Diagrams  Chp 7, 10 and online resources Smith
4 O-O Analysis and Design: State & Package Diagrams Chp 10 and online resources Smith
5

Applications Development, data dictionaries and designing databases 

Chp 8 & 13 and online resources Ramakrishnan
6 Applications Development and Designing Effective Output Chp 11 and online resources Ramakrishnan
7

Applications Development and Designing Effective Input 

Chp 12 and online resources Ramakrishnan
8 Applications Development and Human-Computer Interaction Chp 14 and online resources Ramakrishnan
9

Applications Development and Process Specifications and Structured Decisions

Chp 9 and online resources

Ramakrishnan
10 Applications Development and Agile Modelling and Prototyping Chp 6 and online resources Ramakrishnan
11 Project Management Chp 3 Smith
12 Quality Assurance and Implementation Chp 15 & 16 Smith
13 Revision   Smith & Ramakrishnan

Learning and Teaching Activities

Lectures

Lectures from staff

Workshops

The workshops provide a combination of tutorial exercises and practicals led by tutors. These workshops are designed to prepare you for all of your assessments by providing individual and group activities that explore the concepts, tools and methods used in requirements gathering, modelling, design and development of applications.

Assignments submission

Submission of assignments related to specific tasks - mix of group and individual assignments.

Exams

A final exam will assess individual learning

Policies and Procedures

Macquarie University policies and procedures are accessible from Policy Central (https://staff.mq.edu.au/work/strategy-planning-and-governance/university-policies-and-procedures/policy-central). Students should be aware of the following policies in particular with regard to Learning and Teaching:

Undergraduate students seeking more policy resources can visit the Student Policy Gateway (https://students.mq.edu.au/support/study/student-policy-gateway). It is your one-stop-shop for the key policies you need to know about throughout your undergraduate student journey.

If you would like to see all the policies relevant to Learning and Teaching visit Policy Central (https://staff.mq.edu.au/work/strategy-planning-and-governance/university-policies-and-procedures/policy-central).

Student Code of Conduct

Macquarie University students have a responsibility to be familiar with the Student Code of Conduct: https://students.mq.edu.au/study/getting-started/student-conduct​

Results

Results shown in iLearn, or released directly by your Unit Convenor, are not confirmed as they are subject to final approval by the University. Once approved, final results will be sent to your student email address and will be made available in eStudent. For more information visit ask.mq.edu.au.

Special consideration policy of the Department of Computing:

http://comp.mq.edu.au/undergrad/policies/special_consideration_policy.htm

Student Support

Macquarie University provides a range of support services for students. For details, visit http://students.mq.edu.au/support/

Learning Skills

Learning Skills (mq.edu.au/learningskills) provides academic writing resources and study strategies to improve your marks and take control of your study.

Student Services and Support

Students with a disability are encouraged to contact the Disability Service who can provide appropriate help with any issues that arise during their studies.

Student Enquiries

For all student enquiries, visit Student Connect at ask.mq.edu.au

IT Help

For help with University computer systems and technology, visit http://www.mq.edu.au/about_us/offices_and_units/information_technology/help/

When using the University's IT, you must adhere to the Acceptable Use of IT Resources Policy. The policy applies to all who connect to the MQ network including students.

Graduate Capabilities

Creative and Innovative

Our graduates will also be capable of creative thinking and of creating knowledge. They will be imaginative and open to experience and capable of innovation at work and in the community. We want them to be engaged in applying their critical, creative thinking.

This graduate capability is supported by:

Learning outcome

  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Assessment tasks

  • Workshop Participation
  • Evaluating Conceptual Design
  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Capable of Professional and Personal Judgement and Initiative

We want our graduates to have emotional intelligence and sound interpersonal skills and to demonstrate discernment and common sense in their professional and personal judgement. They will exercise initiative as needed. They will be capable of risk assessment, and be able to handle ambiguity and complexity, enabling them to be adaptable in diverse and changing environments.

This graduate capability is supported by:

Learning outcomes

  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Assessment tasks

  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Commitment to Continuous Learning

Our graduates will have enquiring minds and a literate curiosity which will lead them to pursue knowledge for its own sake. They will continue to pursue learning in their careers and as they participate in the world. They will be capable of reflecting on their experiences and relationships with others and the environment, learning from them, and growing - personally, professionally and socially.

This graduate capability is supported by:

Learning outcomes

  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Assessment tasks

  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Discipline Specific Knowledge and Skills

Our graduates will take with them the intellectual development, depth and breadth of knowledge, scholarly understanding, and specific subject content in their chosen fields to make them competent and confident in their subject or profession. They will be able to demonstrate, where relevant, professional technical competence and meet professional standards. They will be able to articulate the structure of knowledge of their discipline, be able to adapt discipline-specific knowledge to novel situations, and be able to contribute from their discipline to inter-disciplinary solutions to problems.

This graduate capability is supported by:

Learning outcomes

  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Assessment tasks

  • Workshop Participation
  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Critical, Analytical and Integrative Thinking

We want our graduates to be capable of reasoning, questioning and analysing, and to integrate and synthesise learning and knowledge from a range of sources and environments; to be able to critique constraints, assumptions and limitations; to be able to think independently and systemically in relation to scholarly activity, in the workplace, and in the world. We want them to have a level of scientific and information technology literacy.

This graduate capability is supported by:

Learning outcomes

  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Assessment tasks

  • Workshop Participation
  • Evaluating Conceptual Design
  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Problem Solving and Research Capability

Our graduates should be capable of researching; of analysing, and interpreting and assessing data and information in various forms; of drawing connections across fields of knowledge; and they should be able to relate their knowledge to complex situations at work or in the world, in order to diagnose and solve problems. We want them to have the confidence to take the initiative in doing so, within an awareness of their own limitations.

This graduate capability is supported by:

Learning outcomes

  • Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Assessment tasks

  • Workshop Participation
  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Effective Communication

We want to develop in our students the ability to communicate and convey their views in forms effective with different audiences. We want our graduates to take with them the capability to read, listen, question, gather and evaluate information resources in a variety of formats, assess, write clearly, speak effectively, and to use visual communication and communication technologies as appropriate.

This graduate capability is supported by:

Learning outcomes

  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.
  • Demonstrate an understanding of the concepts and tools needed to successfully design and build a mobile application with a database-centric approach

Assessment tasks

  • Workshop Participation
  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Engaged and Ethical Local and Global citizens

As local citizens our graduates will be aware of indigenous perspectives and of the nation's historical context. They will be engaged with the challenges of contemporary society and with knowledge and ideas. We want our graduates to have respect for diversity, to be open-minded, sensitive to others and inclusive, and to be open to other cultures and perspectives: they should have a level of cultural literacy. Our graduates should be aware of disadvantage and social justice, and be willing to participate to help create a wiser and better society.

This graduate capability is supported by:

Learning outcome

  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.

Assessment tasks

  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Socially and Environmentally Active and Responsible

We want our graduates to be aware of and have respect for self and others; to be able to work with others as a leader and a team player; to have a sense of connectedness with others and country; and to have a sense of mutual obligation. Our graduates should be informed and active participants in moving society towards sustainability.

This graduate capability is supported by:

Learning outcome

  • Demonstrate ability to communicate software requirements and designs, clearly and effectively.

Assessment tasks

  • Requirements and Modelling
  • App. Dev. Proj - Design
  • App. Dev. Proj - Development
  • Final Examination

Changes from Previous Offering

Students will work on examples and problems in mixed classes to prepare them for the assignments which will target similar (but not the same) problem.

Students will learn how OO analysis and design relates to OO software development and also create non-OO analysis and designs and associated code.

Assignment 2 will be delivered in two phases and will be developed on react native in contrast to Android Studio

Workshop attendance and participation will NOT be a hurdle task. Workshop participation is worth 10% and final examination 45%

 

 

Assignment Extension - Policy

No extensions will be granted. Late assignments will be accepted up to 72 hours after the submission deadline.  There will be a deduction of 20%* of the total available marks made from the total awarded mark for each 24 hour period or part thereof that the submission is late (for example, 25 hours late in submission – 40% penalty). This penalty does not apply for cases in which an application for special consideration is made and approved. 

Changes from Last Year

 

 

Standards and Grading

In order to pass the unit, you must obtain a total mark of 50% or higher in the unit. The final mark will be the summation of the marks you have received for assessments including the final exam.

ISYS254 will be graded according to the following general descriptions of the letter grades as specified by Macquarie University.

• High Distinction (HD, 85-100): provides consistent evidence of deep and critical understanding in relation to the learning outcomes. There is substantial originality and insight in identifying, generating and communicating competing arguments, perspectives or problem solving approaches; critical evaluation of problems, their solutions and their implications; creativity in application as appropriate to the discipline.

• Distinction (D, 75-84): provides evidence of integration and evaluation of critical ideas, principles and theories, distinctive insight and ability in applying relevant skills and concepts in relation to learning outcomes. There is demonstration of frequent originality in defining and analysing issues or problems and providing solutions; and the use of means of communication appropriate to the discipline and the audience.

• Credit (Cr, 65-74): provides evidence of learning that goes beyond replication of content knowledge or skills relevant to the learning outcomes. There is demonstration of substantial understanding of fundamental concepts in the field of study and the ability to apply these concepts in a variety of contexts; convincing argumentation with appropriate coherent justification; communication of ideas fluently and clearly in terms of the conventions of the discipline..

• Pass (P, 50-64): provides sufficient evidence of the achievement of learning outcomes. There is demonstration of understanding and application of fundamental concepts of the field of study; routine argumentation with acceptable justification; communication of information and ideas adequately in terms of the conventions of the discipline. The learning attainment is considered satisfactory or adequate or competent or capable in relation to the specified outcomes.

• Fail (F, 0-49): does not provide evidence of attainment of learning outcomes. There is missing or partial or superficial or faulty understanding and application of the fundamental concepts in the field of study; missing, undeveloped, inappropriate or confusing argumentation; incomplete, confusing or lacking communication of ideas in ways that give little attention to the conventions of the discipline.

 

L.O 1

Developing

Functional(P)

Proficient (Cr-D)

Advanced (D-HD)

Practice the key phases of the software development life cycle (SDLC) including requirements engineering, analysis, design, basic development and testing and demonstrate understanding of alternative SDLC lifecycle models.

Basic knowledge of the names of the phases of the traditional system development life cycle but lack of understanding of alternative life cycles, how the phases relate, artefacts produced and models used in each phase or how the life cycle is used to turn a real world problem into a software solution.

Awareness of the phases of the traditional system development life cycle some understanding of alternative life cycles, how the phases relate, artefacts produced and models used in each phase or how the life cycle is used to turn a real world problem into a software solution.

Understanding of traditional and alternative life cycles, how the phases relate, artefacts produced and models used in each phase or how the life cycle is used to turn a real world problem into a software solution. Awareness of issues such as quality, project management, methodologies.

Deep understanding of traditional and alternative life cycles, how the phases relate, artefacts produced and models used in each phase or how the life cycle is used to turn a real world problem into a software solution. Appreciation of a range of issues such as quality, project management, design tradeoffs and choices, methodologies and how they impact on the life cycle, the project, the team and software developed.

L.O. 2

Developing

Functional

Proficient

Advanced

Demonstrate an understanding of the concepts and tools needed to successfully design and build database-centric application programs using object-oriented and traditional methods and project management techniques.

Ability to use a CASE tool to create models but with limited understanding of how the models connect and how the tool can be effectively used to ensure model consistency.

Ability to use a CASE tool to create models, understanding of how the models connect and some understanding of how the tool can be effectively used to ensure model consistency.

Ability to use a CASE tool to create models, understanding of how the models connect and how the tool can be effectively used to ensure model consistency. Ability to use a CASE tool to create models, understanding of how the models connect and how the tool can be effectively and efficiently used to ensure model consistency. Familiarity with extended features of the tools and the role that these features can play in supporting the development of software.

L.O.3

Developing

Functional

Proficient Advanced

Demonstrate ability to communicate software requirements and designs clearly and effectively.

Aware of documentation standards and notations but not able to apply them to the appropriate situation.

Able to follow a standard (e.g. IEEE standard for SRS) and appropriately use modelling notations. Able to document and read documentation concerning a software application.

Able to communicate at a functional level and also able to verify and validate documentation produced by themselves and others.

Able to communicate at a proficient level and also able to demonstrate a deep understanding of the role and relationship of various documents, activities, processes and roles which make up software development teams, projects, processes and products.