Software Engineering: Processes and Methods
Assignment - 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.
Learning Outcomes
The following course learning outcomes are assessed by completing this assessment:
- explain how models are used to assist in analysing and modifying existing business systems;
- identify appropriate models for given scenarios;
- develop various models using a professional CASE tool;
- produce Design models using Structured (Traditional) Approach;
- perform Object Oriented Analysis and Design to construct various object models used to communicate the scope and requirements of the project; and
- 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.