Beruflich Dokumente
Kultur Dokumente
1. The UI Designs should be aligned correctly and follow the same UI theme for all the forms.
2. Buttons and Error Messages must be labelled in the correct grammar.
3.Reports and Graphs should match to the data.
4. Database must be built in way it can be integrated with other Module Data Base
5. Business Rules ( Calculations and Programming Logic ) must follow a understandable
Acceptance Criteria Standard.
6.System should not stop working but provide Error Messages and Hints about the Failure.
1.Please refer to the Mix Use Case UML diagrams in the shared location.
2. Mock up Screens
3.Test Reports from the Equipments
Attachements 4. Legacy System Access details
# @PO in what way would the other modules be linked to this one?
# @PO is there a limit to Database tables
#@PO should the DB be recreated?
Comments #@ PO are there any dependencies on or to this Module.
ed in the Labs at DOT.
/InitialBuild/
esible in
ocation
d location.
one?
Feature ID #003
Feature Title Build Field Module Functionality
Area Super Pave
Type New Feature
The development will build SuperPave module that will be used in the Labs at DOT.
1. Designing the UI for the Forms, Reports,Graphs and Search.
2.Create a Data base that will incorporate entire Data that the user can enter.
Description 3.Build Functionality to input various lab results in the Application.
4.Create a functionality for Technicians to be able to Upload equipment results in the
form of Excel sheets.
1. The UI Designs should be aligned correctly and follow the same UI theme for all the
forms.
2. Buttons and Error Messages must be labelled in the correct grammar.
3.Reports and Graphs should match to the data.
Acceptance Criteria 4. Database must be built in way it can be integrated with other Module Data Base
5. Business Rules ( Calculations and Programming Logic ) must follow a understandable
Standard.
6.System should not stop working but provide Error Messages and Hints about the
Failure.
Target Date Priority (1-10) Effort /Months Business Value (1-10)
2/20/2018 7 3 10
Status Details
Time Criticality Value Area Current Status
Medium Business Under Review
# The Main Page is built and can be accessed at c:/SpuperPave/InitialBuild/
#The Business Rules ( Calculations and Other practices) are accesible in
c:/SpuperPave/Documentation/Field Module
Development Details #Develoment team can access Mockup screens in the Shared Location
1.Please refer to the Mix Use Case UML diagrams in the shared location.
2. Mock up Screens
Attachements 3.Test Reports from the Equipments
4. Legacy System Access details
# @PO in what way would the other modules be linked to this one?
# @PO is there a limit to Database tables
#@PO should the DB be recreated?
Comments
Feature ID #004
Feature Title Build Mix Module Functionality
Area Super Pave
Type New Feature
The development will build SuperPave module that will be used in the Labs at DOT.
1. Designing the UI for the Forms, Reports,Graphs and Search.
2.Create a Data base that will incorporate entire Data that the user can enter.
#Data from Lab and Field should be flowed into Mix for the Technicians to be able
to estimate the right blend
3.Build Functionality to input various lab results in the Application.
4.Create a functionality for Technicians to be able to Upload equipment results in
Description the form of Excel sheets.
5. The complex functionality displays data from Lab and Field for the technicians to
compare the results and get the estimated blend calculations.
1. The UI Designs should be aligned correctly and follow the same UI theme for all
the forms.
2. Buttons and Error Messages must be labelled in the correct grammar.
3.Reports and Graphs should match to the data.
4. Database must be built in way it can be integrated with other Module Data Base
Acceptance Criteria 5. Business Rules ( Calculations and Programming Logic ) must follow a
understandable Standard.
6.System should not stop working but provide Error Messages and Hints about the
Failure.
1.Please refer to the Mix Use Case UML diagrams in the shared location.
2. Mock up Screens
3.Test Reports from the Equipments
Attachements 4. Legacy System Access details
# @PO in what way would the other modules be linked to this one?
# @PO is there a limit to Database tables
#@PO should the DB be recreated?
Comments
User Story ID Feature ID Story Title Type ( New - Old)
#002
Technicians should be able to create Projects, which will take alpha numeric
numbers.
The Projects thus created would be saved in the Database Table
The projects will have Index number which will be a Project ID a Primary
Key -> in a relational database.
Projects will not have Duplicate names.
Technicians should be able to Delete the Project. The Project will delete
entire information related to it.
There will be no information related to the Project once it is deleted.
The Technician can add the same Project again.
Acceptance Criteria Priority Business Value Effort - Story Points