RECENT ASSIGNMENT

Assignment 2 – Group Assignment
Overview
The purpose of this assignment is to provide students with experience in structured and object-oriented analysis and design. This assignment is to be completed by groups of two students. Each group is to work together, distribute work equally and submit one group submission. The submission is to include an individual statement of contribution signed by each student that identifies who contributed to each part of the solution and which parts were completed together.
The two students in the group need to examine their Individual Assignment submissions and, as a group, combine ideas from each member's case study completed in Assignment 1 to form a new case study. They will then need to perform further analysis and design based on the new case study.
Timelines and Expectations
Marks: Assignment will be assessed based on a mark out of 100
Percentage Value of Task: 30% of the course marks
Due: Week 11, Friday 5:00pm
Minimum time expectation: 30 hours
This is a group (2 students only) assignment. Both students are expected to contribute equally to the assignment submitted.
Learning Outcomes Assessed
The following course learning outcomes are assessed by completing this assessment:
• K1. explain how models are used to assist in analysing and modifying existing business systems;
• S1. identify appropriate models for given scenarios;
• S2. develop various models using a professional CASE tool;
• S3. produce Design models using Structured (Traditional) Approach;
• S4. perform Object Oriented Analysis and Design to construct various object models used to communicate the scope and requirements of the project; and
• A1. write integrated reports, using appropriate models, providing detailed analysis of given textual scenarios
Assessment Details
Background
The two students in the group need to examine their Individual Assignment submissions and, as a group, combine ideas from each member's case study completed in Assignment 1 to form a new case study. The new case study should then be used to identify all necessary components of the new system and then used to complete structured and object-oriented analysis and design tasks in two analysis cycles toward the development of part of the proposed system. The tasks to be completed are identified in the following section.
Assessable Tasks/Requirements
Cycle 1: Events and Structured Analysis with Data Flow Diagrams
A. Students should extract useful and relevant information about the scope of the system to be addressed from the case study and list all possible events to which the system must respond. Event table entries should be created and these entries should include the event, event type, trigger, source, activity/use case, response(s), and destination(s).
An example of the layout for this answer might be:
Event Event
Type
Trigger
Source Activity/Use
Case
Response
Destination
B. Students should then use all the understanding of the system they have so far from the case background (refer assignment 1), the events list and the draft scope documentation they each prepared in Assignment 1 to construct the Context Diagram for the complete overall system for the organization.
C. In order to develop an appropriate Level 0 Data Flow Diagram, the list of business events should be examined for possible logical groupings (e.g., which events are closely related?). Logical groupings or associations of events can suggest subsystems or major processes that make up the system for the organization.
Students should then create the Level 0 Data Flow Diagram for the organization.
D. Level 1 Data Flow Diagrams (child diagrams) should be constructed by exploding major processes from the level 0 DFD. Students need to choose two different processes from the level 0 DFD and produce a detailed Data Flow analysis on each process.
Cycle 2: Object Oriented Analysis and Design Modelling
A. A Use Case Model for the complete overall system for the organization and a fully developed Use Case
Scenario (description) with exception conditions for ONE of the major use cases in the model, should be created.
B. Flow of events essentially documents the functionality of a use case, i.e., what the use case can do from an end-user's perspective. A scenario is an instance of a use case and it emphasizes how a use case incorporates user activities as well as interactions of related objects. Hence it provides a basis for drawing Activity diagrams and Sequence diagrams.
a. Students should develop an Activity Diagram for the use case chosen in part A of this cycle.
b. Students should also develop a System Sequence Diagram (SSD) for the complete overall system and a Sequence Diagram (SD) for their selected use case.
C. A Domain Model Class Diagram for the complete overall system should also be constructed.
D. Statechart diagrams are drawn to design and describe internal activity, or method logic, of system objects and to develop a further understanding of such processes and behavior. A Statechart Diagram for any ONE of the major objects in their case study system should be created.
E. Finally, students must design any ONE of the major report(s) required as output to the relevant personnel in the organization. Students should refer to the Event-Response table from part 1 as part of this task.
Evidence of Teamwork
Note that this is a group assignment and good teamwork is ESSENTIAL. All tasks must be evenly distributed and assigned among group members and all completed tasks must be reviewed by both members. Marks to individual group members may vary if “lack of participation or involvement” by the other member is reported or if the quality of individually assigned tasks varies in standard. Each group member’s name must be shown with the diagrams/charts the group member has completed individually.
Submission
An electronic copy of the Group Assignment should be submitted via Moodle. Partner students should refer to their course lecturer for submission instructions. The Course Description should be referenced for information regarding late assignments, extensions, special consideration, and plagiarism. All academic regulations can be accessed via the university’s website, see: http://federation.edu.au/staff/governance/legal/feduni-legislation/feduni-statutes-andregulations
The assignment should be submitted in a pdf document in a formal report format (with school cover page attached) containing brief walkthrough/discussions of the diagrams/charts along with those diagrams/charts/drawings on or before the due date. Students should use a CASE tool such as Enterprise Architect as appropriate. Note that all diagrams are to be drawn using appropriate conventions, preferably those used by your textbook (Kendall, K.E. & Kendall, J.E. (2014). Systems Analysis and Design 9/E. Pearson Education Limited, Harlow, England) l. All files, including the completed statement provided on the next page, should be zipped and uploaded to Moodle. Your lecturer/tutor may have further instructions.
The submitted work must also adhere to academic writing standards and show evidence of quality written expression as outlined in the University General Guide to Writing and Study Skills and General Guide to Referencing:
• http://federation.edu.au/__data/assets/pdf_file/0018/190044/General-Guide-to-Writing-and-Study-Skills.pdf
• https://federation.edu.au/__data/assets/pdf_file/0020/313328/FEDUNI-GENERAL-GUIDE-TOREFERENCING-2016-EDITION_ed.pdf
Individual Statement of Contribution
Student Number:
Student Name:
I have individually prepared the solution for the following questions in the Group Assignment
(Assignment 2) for ITECH2101:
-
-
-
-
I have been involved in group collaboration, discussion and review of the following questions in the Group Assignment (Assignment 2) for ITECH2101:
-
-
-
-
I feel that overall, my contribution to the Group Assignment (Assignment 2) for ITECH2101
would equal ________% of the total work submitted.
The other member in my group was:
Name:
Student Number:
Signature
Date
Marking Criteria/Rubric
A student’s work will be assessed based on answers to all parts of the Assessable Tasks/Requirements and a student’s overall mark may be adjusted based on their contribution to the group.
Student ID Student Name Marker Date
Criteria Maximum Marks Marking Scale
Poor
Excellent
1…………max
Cycle 1, Item A (1A) - Events Table
• Correct identification of maximum possible number of core events
• All other associated information (Type of Events, Triggers, Activity/Use Case, Responses and Destinations)
• Correct naming/language conventions.
8
1B - Context Diagram
• Appropriate number of External Entities/Agents and Data Flows
• Appropriate naming, numbering and drawing conventions
8
1C - Level 0 DFD
• Appropriate number of Processes, Data Flows and Data Stores
• Correct naming, numbering and drawing conventions
• Level 0 appropriately balanced, levelled and made consistent
12
1D - Level 1 DFD for 2 selected Processes -
• More detailed with appropriate number of exploded Processes, relevant Data Flows, associated External Agents and Data Stores
• Correct naming, numbering and drawing conventions
7
2A - USE Case Model
• Complete with correct Use Cases and Actors
• Appropriate interactions
• Correct use of naming and drawing conventions
7
2A - Use Case Scenario for the selected Use Case
• Fully developed including exception conditions
• Correct use of conventions
7
2Ba - Activity Diagram for the selected Use Case
• Appropriate identification and flow of activities, and consistent to the Use Case selected
• Correct use of naming and drawing conventions
8
2Bb - System Sequence Diagrams (SSD)
• Correct SSD for the overall system
• Appropriate actor(s) and messages identified in correct sequence
• Correct use of naming and drawing conventions
5
2Bb - Sequence Diagrams (SD) for the selected Use Case
• Correct SD for the selected Use Case
• Appropriate objects, actors and messages identified in correct sequence
• Correct use of naming and drawing conventions
7
2C - Domain Model Class Diagram for the overall system
• Appropriate number of Classes with attributes and some major methods
• Appropriate multiplicities, associations including generalization/specialization
• Correct naming/drawing conventions
12
2D - Statechart Diagram for the selected object
• Appropriate number of States, State Transitions, and paths- independent/concurrent
• Correct use of naming/drawing conventions
7
2E - Design of one of the major Reports as Output
• Contains all appropriate information as required
• Use of appropriate Printed Report design considerations including clear layout and formatting including appropriate headings
7
Presentation of the document along with assumptions, and Walkthroughs/discussions
5
Out of
100
Based on contribution statements, these totals may be adjusted if there is inequity in student contributions.
Final marks to be adjusted to equivalent percentage and scaled to a Total Mark out of 30.
Student Number Name Final Mark (/30)
General Comments:
Feedback
Feedback will occur through Moodle within two weeks of the submission date