deliverables and specifications
Document Revision and History
|
Document Purpose |
Setting the engineering policies that guides the implementation of processes and work products generation |
|
Generation Date |
1 May 2018 |
|
Modification Date |
September 2, 2015 |
|
Generated By |
G.Ghoniem Abdel Azim,DM |
|
Update By |
G.Ghoniem Abdel Azim,DM |
Contents
2. Out-source project Expected deliverables
3. Learning Objects specifications
|
S# |
Tool |
Description |
|
1. |
EA |
Used for modelling the business requirements, analysis, and solution
architecture. |
|
2. |
.Net 2013 .Net 2015 |
-
Used for
developing desktop, and web applications -
MVC for
web applications. -
Jscript
,JQuery, Bootstrap, and AnjularJS for client side |
|
3. |
SQL-Server 2012 or later |
Used as a content media for the database layer |
|
4. |
Objective C |
Development tool for iOS applications |
|
5. |
Android SDK |
For developing android Apps |
|
S# |
Required Doc |
Meaning |
When |
|
1.
|
Project
plan |
-
Releases and iteration, time-boxed model. -
Iteration time-Box = 2 Weeks |
At the
start of the project |
|
2.
|
Retrospectives |
Iteration
reviews at end of each iteration in order to review progress. |
End of
each iteration |
|
3.
|
Deployment
model |
UML model
represents where physically the software components will be deployed, how to
connect them together, software and hardware requirements, and deployment
specifications. |
At the
start of the project |
|
4.
|
Use case
models |
UML model
to represent the high level requirements that required to be used by the
system users(Actors). |
At the
start of the project |
|
5.
|
Use cases |
The
analysis of the use case model by adding its pre-post conditions, scenarios
and exceptions. |
Iteratively |
|
6.
|
Class
diagram |
-
What is the required building blocks to achieve the given requirements. -
You should provide the direct relation between the use cases and the
class diagram |
Iteratively |
|
7.
|
Component
diagram |
Define the
high level building blocks and the relations between them. |
Iteratively |
|
8.
|
Sequence
diagram |
For each
scenario, you should provide the main components interaction process to
achieve the required process |
Iteratively |
|
9.
|
Test cases |
-
The built test cases according to the given UI, GFX and use cases. -
You should provide the direct relation between the test case and the
UI element and use case. |
Iteratively |
|
10.
|
Unit test
cases |
-
The test for the source code. -
You should include the integration test on the integration layer if
found. |
Iteratively |
|
11.
|
UI/UX |
The
proposed user interface for the system |
Iteratively
or as agreed |
|
12.
|
GFX |
The proposed graphics for the system |
Iteratively |
|
13.
|
Release notes |
The current release report including the delivered features, and the
known bugs. |
Iteratively |
|
S# |
Attribute |
Media
format |
Size in MB |
Duration in Minutes |
Comment |
|
1.
|
Video |
Mp4 |
<=1,200k |
<= 5
Min |
The size
and duration is recommended, while the Media format is a constraint |
|
2.
|
Image |
- Svg for the Info graph -Png for the remaining |
<=80k |
NA |
The size
is recommended, while the Media format is a constraint |
|
3.
|
Sound |
Mp3 |
<=900k |
<= 5
Min |
The size
and sound duration is recommended, while the Media format is a constraint |
|
4.
|
unit size |
- |
<=800
MB |
- |
It’s a
constraint overall the exported unit, so you should utilize your overall
building blocks. |
For more clarifications about the LO templates, kindly visit the following path: