System Changes - Lifecycle

Requester
1.) Title:
You need to give a name to this task. Think about some name that
could remember you in the future, what about is this task.
2.) Goals:
What do you want to achieve with these changes? What will happen
differently after this is implemented?
3.) Afected Systems:
Today, which will be affected systems, under your perspective?
4.) Description \ Summary
Make description about what you need to implemented. What should
happen, where, when and who.
5.) Screenshots
If is possible, give us some screenshots over the olde version, making
your changes, even you use your hands and a pen.
6.) Data dictionary
Please, describe your fields (if is possible), and the source for each
one.
Field name
First Name
Age
TotalComission

Type
String
Number
Number

SubTotal

Number

Active
ReadOnly
False

Source
DB - Owner
Type by user
Calculated (sum
all commissions
in page)
Calculated (Fee
+ tax +
firstamount)

Systems Analyst
1.) Domain
2.) Analysis of Impact and Feasibility
3.) High Level Logic
4.) Use case diagram
5.) Model Entity Relation X Data Class Diagram
6.) Sequence diagram
7.) Prototype

Rua 05 n 945 - Sala 02 Mezanino - Setor Oeste - Goinia GO | CEP: 74.115-060

Fone: +55 (62) 3942-7338 | Email: ViaAppiaConstre@gmail.com
http://www.ViaAppiaConsultoria.com.br

Developer
1.) Summary
Describe all changes you feel important or unusual.
2.) Low Level Logics
Describe all used low level logic that is not a regular one.
3.) DB Scripts
Name of DB scripts you had created.
4.) Deployment specials
Web.config keys, or any other important information to the
deployment process.
5.) Test cases
List the test cases here (Leads, Links etc..)

Rua 05 n 945 - Sala 02 Mezanino - Setor Oeste - Goinia GO | CEP: 74.115-060

Fone: +55 (62) 3942-7338 | Email: ViaAppiaConstre@gmail.com
http://www.ViaAppiaConsultoria.com.br