Assessment item 2 - Elaboration phase
Value: 35%
Due date: 27-April-2018
Return date: 18-May-2018
Length: Word length 1800 to 2000
Submission method options
Alternative submission method
Task
In this assessment item, you are required to provide the detailed architecture and design of the system presented in Assessment Item 1 in report form. The total number of words should be between 1800—2000. Please note the words included in the diagrams/figures will not be counted. Amongst the information sought are answers to the following questions:
Questions you need to address are:
1. Identify and briefly describe the main functional and non-functional requirements for the major systems areas of the case study.
• List the functional requirements of each sub system. This could be an improved version from the first assignment.
• List the non-functional requirements on different sub categories. Please refer to week-2 lesson.
2. Draw a use case model for the information system. Write brief Use Case description for each Use Case in the diagram. Write one fully developed Use Case description for one of the important Use Cases identified. Select an important Use Case that is key part of the system, not a basic simple Use Case.
• Draw use case diagrams for all systems – draw a separate use case diagram for each sub system
3. Draw a UML domain model class diagram for all systems in your chosen case study. Be as specific and accurate as possible, given the information provided. If needed information is not given, make realistic assumptions.
• Draw a UML domain model class diagram for all systems – Draw a single domain model class diagram for the whole system.
4. For each of the five design activity of SDLC, list and briefly describe some specific tasks required for each design activities (i.e., describing the environment, designing application components, user interfaces, the database, and software methods.
• Briefly describe the below (refer to lecture notes on Systems Design):
? describing the environment - ? designing application components -
? user interfaces - ? the database - and
? software methods -
Rationale
This assessment tasks covers the fundamental concepts of object modeling, use cases, dynamic models and has been designed to ensure that you are engaging with the subject content on a regular basis. The purpose of the assessment task is to strengthen the student's skill in developing a detailed OO design using UML notation, based on a set of user requirements. More specifically it assess your ability to:
• Apply the concepts of object orientation methodology (Learning outcome 1).
• Analyse system requirements to determine the use cases and domain model of the problem domain (Learning outcome 3).
• Create class diagrams and dynamic models with UML notations (Learning outcome
4).
• Perform modeling of various aspects of systems to construct quality diagrams from a case study (Learning outcome 6).
Marking criteria
Criteria HD DI CR PS FL
Q1. Identify and briefly describe the main functional and nonfunctional requirements for the major systems areas of the case study.
(6 Marks)
a)All possible functional and non-functional requirements are identified and described for the major systems areas of the case study. a)All major functional and non-functional requirements are identified and described for the major systems areas of the case study. a)Some functional and non-functional requirements are identified and described for the major systems areas of the case study. a)Few functional and nonfunctional requirements are identified and described for the major systems areas of the case study. a)Functional and nonfunctional requirements are identified with major errors.
Q2. Draw the use case diagrams for all systems in the case study that show all a)Comprehensive explanation about the role of use cases and all use case diagrams are a)Mostly comprehensive explanation about the role of use cases and all use a)Mostly comprehensive explanation about the role of use cases and use case a)Reasonable explanation about the role of use cases and use case a)Major omissions in the explanation.
Criteria HD DI CR PS FL
actors and use cases.
(12 Marks) accurate.One Fully Develped use Case description is accuratley done. case diagrams are mostly accurate. One fully
Developed Use
description is done with minor ommisions diagrams are mostly accurate. Minor omissions only. One fully developed use case description is done with some mistakes. diagrams are not always accurate.
Some omissions only.
Q3. Draw a UML domain
model class diagram for all systems and subsystems in your chosen case study. (6 Marks) a)UML domain
model class diagram is accurate for all systems and subsystems;
identified all possible domain classes and some attributes, showing logical relationships among all domain classes. a)UML domain model class diagram is mainly accurate for all systems and subsystems; identified all possible domain classes
and some
attributes, showing logical relationships among all domain classes.
Some
omissions.
a)UML domain model class diagram is accurate for all systems and subsystems; however domain classes and their attributes are not always accurate, logical relationships have some errors among domain classes. a)UML domain model class diagram is not always accurate for all systems and subsystems; domain classes and their attributes are not always accurate, logical relationships have some errors among domain classes. a)UML domain model class diagram have major omissions
Q4. For each of the five design activities of SDLC, list and briefly describe some specific tasks required for each design
activity (i.e., describing the environment, designing a)All five design
activities of
SDLC are
accurately listed and briefly described some specific tasks required for each design activity. a)All five design activities of
SDLC are mostly accurately listed and briefly described some specific tasks required for each design activity a)Four design activities of
SDLC are accurately listed and briefly described some specific tasks required for each design activity. a)Four design activities of
SDLC are mostly accurately listed and briefly described some specific tasks required for each design activity. a)Less than four design activities of
SDLC are
listed and briefly described some specific tasks required for each design activity.
Major omissions in
Criteria HD DI CR PS FL
application components, user interfaces, the database, and software methods.
(6 Marks)
the explanation.
Presentation and clarity (accuracy, spelling, grammar, punctuation) (5 Marks) b) Fluent writing style appropriate to the assignment with accurate grammar and spelling. Referencing is mainly accurate and according to the APA
standard
b) Mostly Fluent writing style appropriate to assignment with accurate grammar and spelling. Referencing is mainly accurate and according to the APA standard. Most of the references are cited in the text.
b) Mostly fluent writing style appropriate to the assignment with mostly accurate grammar and spelling.
Minor omissions only.
Some attempt in referencing and according to the APA standard. Few references are cited in the text.
b) Writing style not always fluent or well organised and grammar and spelling contain errors. Tried to reference according to
APA
standard and only few references are cited in the text as well.
b) Writing style not fluent or wellorganised, and many grammatical and spelling mistakes.
Presentation
Reports should be submitted is MS Word format, using the CSU referencing style of APA. Diagrams can be created using any available tools.
Online submission via Turnitin is required for this assignment. Details will be provided by your subject lecturer.
Requirements
Students should visit and read the CSU Referencing Policy at http://student.csu.edu.au/study/referencing-at-csu