teaching:su:sad:project
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
teaching:su:sad:project [2012/02/14 10:38] amanj [Assignment 1 [Activity 2] - System Analysis (Deadline: 4 Feb 2012)] |
teaching:su:sad:project [2012/05/18 13:15] (current) amanj [Assignment 2 [Activity 3] – System Design (Deadline: 21 May 2012)] |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| //for this task please take a look at the second page of [[http://www.amanj.me/lectures/su/SAD/ProjectPlanning.pdf | PDF file]]// | //for this task please take a look at the second page of [[http://www.amanj.me/lectures/su/SAD/ProjectPlanning.pdf | PDF file]]// | ||
| - | ===== Assignment 1 [Activity 2] - System Analysis (Deadline: 4 Mar 2012) ===== | + | ===== Assignment 1 [Activity 2] - System Analysis (Deadline: 8 Mar 2012) ===== |
| - | - Identify the requirements. produce a requirement document including (user requirements & system requirements documents) (4 weeks) | + | **The only task:** Identify the requirements. produce a requirement document including (user requirements & system requirements documents) (3 weeks) |
| - | **Task1-** requirements elicitation (due to 19 Feb 2012)(2 weeks) | ||
| - | **Task2-** requirements documentation (due to 26 Feb 2012) (1 weeks) - present in 10 minutes: what techniques you have used? problems and solutions? | + | ===== Assignment 2 [Activity 3] – System Design (Deadline: 23 May 2012) ===== |
| - | + | ||
| - | **Task3-** requirement validation (due to 4 Mar 2012) (1 week) - feedback from the lecturer by showing him the produced documents. | + | |
| - | + | ||
| - | ===== Assignment 2 [Activity 3] – System Design (Deadline: 15 April 2012) ===== | + | |
| **The only task:** Design the system, and the produced document should contain the following: | **The only task:** Design the system, and the produced document should contain the following: | ||
| - Use case diagram for two or more use case scenarios. | - Use case diagram for two or more use case scenarios. | ||
| - | - An activity diagram, showing one scenario. | + | - An activity diagram or a sequence diagram, showing one scenario. |
| - A class diagram (at any level) for the whole system. | - A class diagram (at any level) for the whole system. | ||
| - | - A sequence diagram, showing a single scenario. | + | - A statechart diagram (or more) |
| - The architectural design for your system. | - The architectural design for your system. | ||
| - | - Do not forget, you HAVE TO use two different design patterns and you should be able to explain why you have chose it. | + | - Do not forget, you HAVE TO use two different design patterns and you should be able to explain why you have chosen them. |
| - | **Group Presentation:** present your product, development problems and difficulties (date to be declared) | + | **Group Presentation:** Make a poster of your UML diagrams, Design Pattern decisions and selections and Software Architectural Design |
teaching/su/sad/project.1329215905.txt.gz · Last modified: 2012/02/14 10:38 by amanj
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
