Description
Project Tracker
Project Tracker is a system that allows the instructor to track the work of a group of students on a specific project. At the same time students can use the system to manage their work and with the instructor. Suppose we have a class with enough number of students to be divided into two groups or more, Therefore, the instructor has the ability to assign each student to a specific team and give each member a specific role. Moreover, the instructor can create a project with required specifications and properties such as tasks, time, deliverables, etc. Students in the same team can communicate together by broadcasting a message that appears on all team members’ side. They can also communicate with the instructor.
At any time, students can set the status of a task as to start later on, working on, finished on time, finished with delay, etc. and the instructor can review the task and give feedback for students on the task.
The task has a title, description, progress estimation, start date, end due date, actual end date, or any other suggested properties. The task can be assigned to one or more of the students. Group members or the instructor can put a comment on the task and others can reply to it.
Your team must create four deliverables:
Phase 1: Analysis
At the end of analysis phase, you have to submit
An initial requirements document.
An initial problem description
A tentative project plan.
Each member role in each phase.
For individual submission, each student should submit a text file presents each member contributions in this phase. (Write your thought and don’t share it with others)
Phae2: Design phase:
You need to submit the following:
I. The UML of the system. The UML diagram should have all details such as, attribute, method, relationship, cardinality, etc. Your UML should follow the UML standards, shapes, lines, capital and small word, underlines, etc.Also, you need to create sequence diagram, it shows object interactions arranged in time sequence in the field of software engineering.
For more details: https://en.wikipedia.org/wiki/Sequence_diagram
II. Software Architecture:
-The selected architecture style.
-Why do choose this style?
-Do you think there is any other architecture style that your software can be related to?
III. ER diagram.
Phase 3: Implementation Phase:
In this phase, you need to create the required database, the user interface, and the implementation of the system services. The deliverables in this phase:
I. Database: You have to create the database according to the submitted ER diagram in the previous phase, in case you have any change in the DB design, you need to document it and to discuss why did you make this chage.
II. User interface: the interface should have all features that the system provides for all users (instructors and students).
III. Full system: You have to submit the final version of the system, all features in the system should work correctly. You need to submit well documented system.
Phase 4: System Evaluation and final report:
You need to test your system and document and problem that you find in the system. The final report of the system document all works over all phases.
