1. Background Analysis
1.1. Analysis Process
For this problem domain our research began with some initial brainstorming sessions. Collectively, we thought about how such a system
would work in the real-world, what assumptions might need to be applied, and the types of stakeholders involved. This process highlighted
the experience certain team members have had with similar task management systems. Combining this knowledge with the research we
had carried out into existing project management software, such as Teamwork, helped inform. our thoughts about system design, and how
the user interface could be developed. It also helped clarify some assumptions beyond the brief such as how all projects will be defined by
NERDCO prior to the implementation of the system.
Identifying stakeholders became much clearer once we had completed our first draft of the ER-diagram. This allowed us to visualise the
actions of each user and how they interact with each other within the system. Upon completion of our final draft we were in full agreement
about system functionality and each stage of the design process.
[Team 13] Specification Document [22/11/207]
Page 4 of 13
CSC8005 Software
EngineeringTeam Project 2017-18
1.2. Analysis
The targeted business environment for our system is an SME which employs skilled workers on a project-to-project basis. A typical
example might be a start-up development company within the UK’s growing technology sector where individual team tasks combine to
form. a functioning project. Such an environment might already have an existing process in place to check the completion of individual
team tasks. This could be a manager or team leader who physically signs-off tasks as they are competed, or even a file-based software
system that records tasks specific to one team (such as the implementation of code in web development). While these approaches might
be suitable for work within individual teams, they do not necessarily reflect the task coordination requirements of a larger project.
To overcome this, the integration of our system would allow projects, and their associated tasks, to be coordinated from a central point.
This would ensure that employees are allocated specific tasks for their team and that all tasks essential to a project are delegated in a
systematic manner. It would also serve as an important communication tool between teams and the company as a whole. Not only would
this ease the production of important documents, such as client progress reports, but also inform. workers of the tasks outstanding in a
project. This is important as team members need to know the status of each other’s work, particularly if a task is a prerequisite to another.
Stakeholder Position/Role
Team Member The employees who carry out tasks within a defined team of the company
Team Leader The individual who creates and allocates tasks for each project
Manager The senior person in the company who reviews project progress overall
2. Roles and Deliverables
2.1. Roles – team roles and responsibilities
The allocated roles below are subject to change between team members. There will likely be other tasks required as the projec t develops
which will be assigned equally among all members.
Team member Role
Hussain Albader Evaluation of implemented data and code
Yong Chen Implementation for the main program and database
Rensi Deng Implementation for the main program and database
Shuohan Liu Integration of the system and database
John McGill Produce documentation for the system design and user manual
[Team 13] Specification Document [22/11/207]
2.2. Deliverables – what you will deliver to the customer
A functioning software program delivered on or before 7th May 2018 that allows the client to efficiently manage project-based work. This
includes:
An interactive GUI that is clear, simple and easy to use for all stakeholders involved, and that responds correctly to all user input
Feedback protocols that inform. system users when a task is completed
The ability to review completed tasks and inform. users of impending deadlines
A dynamic system that allows tasks and/or team members to be added/removed
The ability for the manager to add/remove projects
Software that allows the status of projects to be easily reviewed
Clear documentation explaining all aspects of the system design
A user manual, written in plain English, with all technical jargon explained
3. Project Plan
This will be based on the hard deadlines set for the project (module webpage/assignments) – however you should also provide any
agreed soft deadlines determined by your team. All deadlines should be clearly shown and who is responsible for the activiti es, on a
Gantt chart – can draw this in MSProject or Excel. Please ensure the Gantt chart is legible and fits on one page, preferably landscape
view.
Gnatt Chart
4. Hardware and software platforms to be used for developing and running your solution
The software will be developed to work only on computers. The program in which the software will implemented is not yet decided. Mainly we are
planning on using C# and/or PHP as a development platform, since it has some features which supports the kind of software we are developing.
5. References
No references were used in the past weeks of developing our application, since most of the time was around completing the ER diagram, setting
out requirements, deciding roles and what the software will develop into.
6. Definition of terms.
No such definitions have been added to the documentation at this stage.
7. Solution requirements
For each requirement indicate its Priority e.g. High, Medium, Low. As you (your team) are the suppliers of the system you need to provide ECLS
with information on what requirements you will complete within the development of the system. In the supplier c ompliance section your responses
must be Yes, No or Partial coverage of the requirement by the solution you are proposing. If partial you need to specify why you will only deliver
part of the requirement in the Supplier Comment column e.g. if a requirement is high priority and you will not provide this you must give a short
written rationale.
7.1. Functional Requirements
Requirement Priority Supplier
Compliance
(Full, partial
or will not
be
delivered)
Supplier
Comment
-The system should allow the creation and management of tasks
-Tasks can be assigned to team members
H Yes
-Allow members/manager to check the status of a task (or tasks) in
relation to its end date
M Yes
-Create schedules for each team member
L Yes
-Create a schedule for the relevant project
H Yes
-Allow members to communicate (leave comments) with other
members working on the same task
L Yes
-The system should allow for new members to be added or existing
members to be removed
M Yes
-The system should contain an interface that is web-based or windows
based
H Yes
-Show which team members are working on which project
M Yes
-Show the specific tasks each team member is working on
L Yes
-Show if a project is running late or to deadline
H Yes
-Projects should contain one or more tasks
H Yes
-System should contain a database that contains users, tasks, projects
and schedules
H Yes
[Team 13] Specification Document [22/11/207]
7.2. Non-Functional Requirements
8. Requirement Priority Supplier
Compliance
(Full, partial
or will not
be
delivered)
Supplier
Comment
-Reminders should be sent to members whose tasks are about to end
M Yes
-A member should be allowed to have multiple tasks
M Yes
-The system should be user friendly (clear and intuitive)
M Yes
-The system should be accessed and managed by the Team Leader H Yes
-Must offer team leader security protection around task management H Partial Insufficient
technical
knowledge
at the
moment
-It should be integrated and linked to a calendar L Yes
-Checking feedback system with comments and task review should be
embedded
L Partial Insufficient
technical
knowledge
at the
moment
-Each task should have a start and an end date to ensure that project
runs within it’s deadline constraint
H Yes
-The system should be stable and reliable for users with long MTBF M Partial Insufficient
technical
[Team 13] Specification Document [22/11/207]
knowledge
at the
moment
-It should facilitate data longevity and integrity H Yes
-The system must meet any relevant Employee Rights and Data
Protection laws
H Yes
-Should offer ease of scalability should the program size need to
increase/decrease in the future
L No An addition
that the
client may
want to use
in the future
-Offer clear and concise documentation (user manual) M Yes
NB: Compliance –Comments can relate to priority level and the reason for it e.g. we will only deliver part of this functionality at this time as it is low
priority. Generally the team should aim to deliver all requirements that are noted as High (H) and Medium priority(M).
9. Other considerations
9.1. Assumptions
1. Projects are handed to the team leader and are not created at the system
2. Team leader is the only one who create tasks and is the only one per team
3. A member belongs to only one team
9.2. Constraints and Dependencies
1. Insufficient technical know how
2. Interface is not yet designed
3. Time constraint
4. Staff limitation
9. Software Design
Requirment1: TaskSchedule is the task list for each member, created by TeamLeader
Requirment2: ProjectSchedule is assigned/canceled to Team by Manager and Manager only, likewise,
TaskSchedule is assigned/canceled to Members by TeamLeader.
Requirment3: Only the Manager have the right of creation and removal of Team, TeamLeader.
Requirment4: Both the Manager and TeamLeader can add or remove Team members.
Requirment5: Display the projectDeadline in ProjectSchedule and taskEndDate in TaskSchedule to show the
status of project. Display memberList that belongs to a particular project to show the number of
team members working on this project.
[Team 13] Specification Document [22/11/207]
Marking Criteria
clearly communicated design decisions - is the approach adopted clearly stated and illustrated?
Textual support for diagrams
Format of the document according to the template
Reasonable changes are clearly stated
Presentation of major screen designs / screen shots
Appropriate use of UML
Contribution Matrix for team work on the specification goes here.