TASK
back to top
Further background
Refer to the Project Vision Document submitted in Assessment Item 1 regarding MyHousing project. In this assignment, you are required to prepare a proposal that describes the various system analysis activities for proposed system.
Complete the Following
Please refer to the marking guide when preparing your response to see what criteria and standards will be used to assess your work and your progress.
Amongst the information sought are answers to the following questions:
1. Identify and briefly describe the functional and non-functional requirements for the proposed system. (3 pages, times new roman, size 12)
2. List the domain classes and their attributes for the proposed system and draw a domain model class diagram. Be creative and add those domain classes you think should be included to make the system useful and appealing.
3. Write a fully developed use case description using any use case for the proposed system.
4. Develop system sequence diagrams for any two use cases, one diagram for each use case. Be creative, use opt frame and alt frame (if-else) where possible.
RATIONALE
back to top
This assessment task will assess the following learning outcome/s:
- be able to compare and contrast the different methodologies of systems analysis and evaluate their appropriateness for different and complex situations.
- be able to distinguish between requirement gathering techniques and combine these appropriately to apply to a real scenario.
- be able to evaluate development requirements and prepare a feasibility proposal based on multi-disciplinary (financial, human resource, technological) analyses.
- be able to formulate and justify system requirement models based on evaluation of given situations.
- be able to assemble the components of a requirements model using the tools and techniques of object oriented or structured systems modelling.
MARKING CRITERIA AND STANDARDS
back to top
| Criteria | High Distinction (HD) | Distinction (DI) | Credit (CR) | Pass (PS) | Fail (FL) |
| 1. Identify and briefly describe the functional and non-functional requirements. 3 Marks | Functional requirements: all nine major business rules are identified and briefly described; Non-functional requirements: seven possible system characteristics are identified and briefly described. (2.55-3.00) | Functional requirements: seven major business rules are identified and briefly described; Non-functional requirements: five possible system characteristics are identified and briefly described. (2.25-2.54) | Functional requirements: five major business rules are identified and briefly described; Non-functional requirements: four possible system characteristics are identified and briefly described. (1.95-2.24) | Functional requirements: three major business rules are identified and briefly described; Non-functional requirements: three possible system characteristics are identified and briefly described. (1.50-1.94) | Identified functional and non-functional requirements are wrong and no or little description. (0.00-1.49) |
| 2. List the domain classes and their attributes for the proposed system and draw a domain model class diagram. 6 Marks | All possible domain classes and their attributes are identified; domain model class diagram is accurate for the system, showing logical relationships among all domain classes. (5.10-6.00) | Most of the domain classes and their attributes are identified; domain model class diagram is mostly accurate for the system, showing logical relationships among all domain classes. (4.50-5.09) | Major domain classes and their attributes are identified; domain model class diagram is mostly accurate for the system, showing logical relationships among all domain classes. Only some omissions. (3.90-4.49) | Few domain classes and their attributes are identified; domain model class diagram is not always accurate for the system; domain classes and their attributes are not always accurate, logical relationships have some errors among domain classes. (3.00-3.89) | Domain model class diagram has major omissions. (0.00-2.99) |
| 3. Write a fully developed use case description using any use case for the proposed system. 4 Marks | All possible compartments of fully developed use case description are identified with accurate description of all compartments. (3.40-4.00) | Major compartments of fully developed use case description are identified with accurate description of major compartments. (3.00-3.39) | Some of the major compartments of fully developed use case description are identified with description of some compartments. (2.60-2.99) | Few compartments of fully developed use case description are identified with description of only few compartments. (2.00-2.59) | Most of the compartments of fully developed use case description are wrong. (0.00-1.99) |
| 4. Develop system sequence diagrams for any two use cases, one diagram for each use case. Be creative, use opt frame and alt frame (if-else) where possible. 4 Marks | System sequence diagrams are accurate using important use cases; identify all input messages, describe the message from the external actor to the system using the accurate message notation, identify any special conditions on input messages (Iteration/loop frame, Opt or Alt frame), identify and add output return values using correct notations. (3.40-4.00) | System sequence diagrams are mostly accurate using important use cases; identify all input messages, describe the message from the external actor to the system using the accurate message notation, identify any special conditions on input messages (Iteration/loop frame, Opt or Alt frame), identify and add output return values using correct notations. (3.00-3.39) | System sequence diagrams are mostly accurate using important use cases; identify all input messages, describe the message from the external actor to the system using the accurate message notation, identify any special conditions on input messages (Iteration/loop frame, Opt or Alt frame), identify and add output return values using correct notations. Some omissions. (2.60-2.99) | System sequence diagrams are not always accurate and only use not important use cases; identify some input messages, describe the message from the external actor to the system using message notation, no special conditions on input messages (Iteration/loop frame, Opt or Alt frame), output return values using incorrect notations. (2.00-2.59) | System seqence diagrms are wrong. (0.00-1.99) |
| Presentation and clarity (accuracy, spelling, grammar, punctuation, figures) 2 Marks | Fluent writing style appropriate to the assignment with accurate grammar and spelling, and high-quality figures drawn using some tools and figures have some captions. (1.70-2.00) | Mostly fluent writing style appropriate to assignment with accurate grammar and spelling, and good-quality figures drawn using some tools and figures have some captions. (1.50-1.69) | Mostly fluent writing style appropriate to the assignment with mostly accurate grammar and spelling. Minor omissions only. Some-quality figures drawn using some tools and figures have some captions. (1.30-1.49) | Writing style not always fluent or well organised and grammar and spelling contain errors. Poor-quality figures drawn using some tools and figures have some captions. (1.00-1.29) | Writing style not fluent or well-organised, and many grammatical and spelling mistakes. Very bad quality figures, copied from others work, no captions. (0.00-0.99) |
| Referencing and Citation
1 Marks |
Referencing is mainly accurate and according to the APA standard. All references are cited in the text. (0.85-1.00) | Referencing is mainly accurate and according to the APA standard. Most of the references are cited in the text. (0.75-0.84) | Some attempt at referencing and according to the APA standard. Few references are cited in the text. (0.65-0.74) | Attempt at referencing but not exactly according to APA standard and only few references are cited in the text. (0.50-0.64) | Referencing is absent/ unsystematic. (0.00-0.49) |
PRESENTATION
back to top
Only task 1 about to identify and briefly describe the functional and non-functional requirements should be 3 pages long, font times new roman, size 12. For other tasks in this assignment, please follow marking criteria and standard. All figures must have suitable caption and cited (if required) within text using APA standard.
REQUIREMENTS
back to top
If any references are required, ensure to use APA referencing to acknowledge the sources that you have used in preparing your assessment. Please refer to the CSU referencing guide http://student.csu.edu.au/study/referencing-at-csu. In addition a very useful tool for you to use that demonstrates how to correctly use in text referencing and the correct way to cite the reference in your reference list can be found at https://apps.csu.edu.au/reftool/apa-6
The post Project Vision Document submitted in Assessment appeared first on My Assignment Online.