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 [2011/12/12 20:23] amanj |
teaching:su:sad:project [2012/05/18 13:15] (current) amanj [Assignment 2 [Activity 3] – System Design (Deadline: 21 May 2012)] |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| * Names and Emails of the team members | * Names and Emails of the team members | ||
| - | ===== The pre-Assignment [Activity 1] (17 Jan) ===== | + | ===== The pre-Assignment [Activity 1] (17 Jan) (Postponed to 11 Feb) ===== |
| **Find** the project description [[project_description|here]] | **Find** the project description [[project_description|here]] | ||
| Line 20: | Line 20: | ||
| **Task1-** Write a proposal and present it to the lecturer (1-page long) . due date: 10 Jan (2 weeks) | **Task1-** Write a proposal and present it to the lecturer (1-page long) . due date: 10 Jan (2 weeks) | ||
| - | **Task2-** Design a project plan: identify tasks, activities and phases. Make a schedule for the project. deadline: 17 Jan (1 week) | + | **Task2-** Design a project plan: identify tasks, activities and phases. Make a schedule for the project. deadline: 17 Jan (1 week). |
| - | ===== Assignment 1 [Activity 2] - System Analysis (Deadline: to be declared) ===== | + | //for this task please take a look at the second page of [[http://www.amanj.me/lectures/su/SAD/ProjectPlanning.pdf | PDF file]]// |
| - | - Identify the requirements. produce a requirement document including (user requirements & system requirements documents) (4 weeks) | + | ===== Assignment 1 [Activity 2] - System Analysis (Deadline: 8 Mar 2012) ===== |
| - | **Task1-** requirements elicitation (2 weeks) | + | **The only task:** Identify the requirements. produce a requirement document including (user requirements & system requirements documents) (3 weeks) |
| - | **Task2-** requirements documentation (1 weeks) - present in 10 minutes: what techniques you have used? problems and solutions? | ||
| - | **Task3-** requirement validation (1 week) - feedback from the lecturer by showing him the produced documents. | + | ===== Assignment 2 [Activity 3] – System Design (Deadline: 23 May 2012) ===== |
| - | ===== Assignment 2 [Activity 3] – System Design (Deadline: to be declared) ===== | + | **The only task:** Design the system, and the produced document should contain the following: |
| - | **Task1-** Architectural design for the system (2 weeks) - present your design and reason your decisions. | + | - Use case diagram for two or more use case scenarios. |
| + | - An activity diagram or a sequence diagram, showing one scenario. | ||
| + | - A class diagram (at any level) for the whole system. | ||
| + | - A statechart diagram (or more) | ||
| + | - 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 chosen them. | ||
| - | **Task2-** More tasks will be defined later | + | **Group Presentation:** Make a poster of your UML diagrams, Design Pattern decisions and selections and Software Architectural Design |
| - | + | ||
| - | **Group Presentation:** present your product, development problems and difficulties (date to be declared) | + | |
| Line 45: | Line 47: | ||
| * In case it becomes evident that the project workload was wildly unbalanced within a team, your instructor may assign differing individual project grades within team members. It is easy to identify who has worked the most. | * In case it becomes evident that the project workload was wildly unbalanced within a team, your instructor may assign differing individual project grades within team members. It is easy to identify who has worked the most. | ||
| - | * Please, submit the delivarables on time. | + | * Please, submit the assignments on time. |
teaching/su/sad/project.1323721390.txt.gz · Last modified: 2011/12/12 20:23 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
