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 |
Who |
Standard |
|
1.
|
Plan |
-
Releases and iteration, time-boxed model. -
Iteration time-Box = 2 Weeks |
At the
start of the Sprint |
Team |
|
|
2.
|
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 |
TL |
|
|
3.
|
Business
Workflow |
Represents
one of: 1.
the solution work flow 2.
Business journey workflow |
1. At the
start of the project 2. Iteratively |
PO/SME |
|
|
4.
|
Use cases |
The
analysis of the use case model by adding its pre-post conditions, scenarios
and exceptions. |
Iteratively |
PO/SME |
|
|
5.
|
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 |
Initially
by PO/SME, and finally by TL |
|
|
6.
|
Component
diagram |
Define the
high level building blocks and the relations between them. |
Iteratively |
Dev team |
|
|
7.
|
Sequence
diagram |
For each
scenario, you should provide the main components interaction process to
achieve the required process |
Iteratively |
Dev team |
|
|
8.
|
State-chart
diagram |
For each
object, create the different states according to the business changes |
Iteratively |
PO/SME Dev team |
|
|
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 |
QC team |
|
|
10.
|
Unit test
cases |
-
The test for the source code. -
You should include the integration test on the integration layer if
found. |
Iteratively |
Dev team |
|
|
11.
|
Sonar
Cloud Code Quality |
-
Improved figures for new services -
Improved figures for old services |
Iteratively |
Dev team |
SAFE CICD |
|
12.
|
UI/UX |
The
proposed user interface for the system |
Iteratively
or as agreed |
UX team |
|