Amanj's Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== The Project Description ======

The best way to learn this course is a full-year team project developing a real system for possibly a real client.

====== Project Guidelines: ======

  - Work in groups of 5 or less. Let me know, if you have difficulties to find partners.
  - The project is divided into two assignments. Each assignment builds on top of the previous. Further, to make the process easier to follow, each assignment is broken down into several tasks. It is therefore suggested that once the groups have been formed you meet with your group members as soon as possible to assign roles and responsibilities and begin the system development process.
  - You get grades based on submission time and quality of the //activities//. Following the //tasks// defined below is recommended to get better results.

Till 20 Dec each group should send:
  * Group Name (if any)
  * The name of the project manager (the team leader)
  * Names and Emails of the team members

===== The pre-Assignment [Activity 1] (17 Jan) (Postponed to 11 Feb) =====

**Find** the project description [[project_description|here]]

**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). 

//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: 8 Mar 2012) =====

**The only task:** Identify the requirements. produce a requirement document including (user requirements & system requirements documents) (3 weeks)


===== Assignment 2 [Activity 3] – System Design (Deadline: 21 May 2012) =====

**The only task:** Design the system, and the produced document should contain the following:

  - 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.

**Group Presentation:** Make a poster of your UML diagrams, Design Pattern decisions and selections and Software Architectural Design



====== IMPORTANT ======

  * 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 assignments on time.
Amanj's Wiki

User Tools

Site Tools

Page Tools
