Sie sind auf Seite 1von 149

Feature ID #002

Feature Title Build Lab 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.
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
Description 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.
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.

Target Date Priority (1-10) Effort /Months Business Value (1-10)


2/10/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 Buiness Rules ( Calculations and Other practices) are accesible in
c:/SpuperPave/Documentation/Mix 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
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.

user can enter.


tion.
quipment results in the form of

me UI theme for all the forms.


grammar.

r Module Data Base


follow a understandable

and Hints about the Failure.

Business Value (1-10)


10

/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.

Target Date Priority (1-10) Effort /Months Business Value (1-10)


4/20/2018 5 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 Buiness Rules ( Calculations and Other practices) are accesible in
c:/SpuperPave/Documentation/Mix Module
Development Details #Develoment team can access Mockup screens in the Shared Location
#Data is higly dependent on the Lab and Field Module.

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)

As a Technician, I should be able to Create Project


#201 New
to input Project Specific Test Results.

As a Technician, I should be able to Create


#202 New
equipments for each Project to input the results.

#002

As a Technician, I should be able to Delete Projects


#203 New
to rectify human errors.

As a Technician, I should be able to provide Project


#204 New
and Binder Information to generate Reports.
New
Description

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 create multiple Equipments called Binders for


Each Project.
The Binders will have a unique name.
They should be indexed and act as a Primary key in the DB.
In order to create a Binder Technicians must select a Project.

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

The Projects should not be similar name.


Alpha Numeric names should be saved.
It will not have Decimal values.
Projects Added would be shown in a Drop Down list. 7 2 5
Technicians should have to click at a Create button to
enable the New Project.
User will get a notification message after the action.

1.Binder will not save duplicate names.


2.Binder will be created only with a Project name.
3. Binder will not be saved if the Project is not Selected. 7 2 8
4. Error messages should match the Business Rules.

1. Entire Information abou the Project is Delete.


2. The Drop Down list is updated once the Delete
Operation is performed. 2 3 13
3. Technician will get a notification that Data and "Are
you sure" message.
Value Area Attachments

Refer to the Mockup screens to create a Form


where the Technicians will input the Project
names.
-Refer to the Document FSD_Super_Pave for
Technical complete requirement
Refer to Alert message document which will have
the Business Rules ( Messages) that should be
displayed

Refer to the Mockup screens to create a Form


where the Technicians will input the Binder names.
-Refer to the Document FSD_Super_Pave for
Technical complete requirement
Refer to Alert message document which will have
the Business Rules ( Messages) that should be
dsiplayed

Please refer to the Data Base diagram to make


check the Project entries in the Data Tables.
Technical Refer to the Buisness Rules document in the
shared folder.
Development Details Related Work

Create a form frm_Project with input fields for Project


Name and buttons.
Connect to the Database using the Connection String. Independent Work
Project Name, ID would be saved in the Data Table.

Create a form frm_Binder with input fields for Binder


Name and buttons. For a Binder to save the User Story #201
Connect to the Database using the Connection String. must be completed first. Binder will only get
Binder Name, ID would be saved in the Data Table. saved when there is a Project ID.

The Delete will be Bottom up.


Dev team will maintain additional documentation of the
Delete Process. Independent Work
It is critical that the right data be deleted.
Comments Assigned To

# @PO specify the Data Table name.


# @PO are there any dependencies on this Data
Table.
# @ PO Provide access to Legacy Data-table.
Value Area Time Criticality Type User Type
Technical High New Feature New
Business Medium Additional Work Additional Work
Numbers Low Comitted
1 Under Review Done
2 Approved Team
3 Comitted Ram
4 Obsolete Shrey
5 Gaurav
6 Nikhil
7 Dinesh
8
9
10

Das könnte Ihnen auch gefallen