Enter Elaboration - Part II

So what all do I want to do in stage of the project?? I ask myself .
here if a list

I have identified the first use cases to touch.these are Enroll , View and Activate . Reasons for choosing these are as follows:
* Pic the ones that make up Architecture
* I mean picking up Login or Find Account does not make sense as they dont really commuicate much architecture.
* Pick the ones that lead you to a skeleton of the Domain Model / the Data Model.
* Also include the ones that test the basic request flow.


Ideally , pick up one use case that tests both the criteria

Enter Eloboration : Part I

Ok So I am ready now.

I have a Good understanding of the Business Use Case Specifications. I really understand the business proceess

I understand the impact of the project to other systems.

I just want to start with doing some real technology stuff.

Best Practice:
1. Have two Technical Documents
a) A Higher level Architecture Document.
b) a more detailed how to guide. Programming


Higher level Architecture Document
Audience : the audience for this document is more general
a) System Administrators
b) Business Architects / BAs
c) Project Managers
d) Developers
e) UI Developers
f) Testers

Focus :
The Focus of this document should be
1. System Intigration.
a) Impact to other systems.
b) Interaction with other systems
c) To capture the nuances of communicating with each system
d) Ideally this document should have a section on each system that we are talking to.
e) From a Front end Launch point of view / From the Back end intigration point of view.
f) This document should talk about the recommended approaches of intigration
2. Information Flow . This document should also talk about "The Owners of information". Which system should own the information and where is the information flowing from and to. Basically we do this. to avoid redundant data and Architecting system better from a Business Point of view.
3. Deployment :General Deployment guideline . It would seem a simple and trivial thing. But sometimes it turns out to be complecated. 1 EAR file , multiple WAR files.

To be continued.....

Use Cases

1. Always start sentences with Actor Names or System Names.
2. Use the correct terminology . As defined in the Project. Dont call a New Business Applicant as Applicant . if you have defined "New Business Applicant " elsewhere.

Best Practice :
1. Use Case and USe Realization :Two Views
2. FR: ID template
3.

Practice : Requirements Gathering
*************************
Dont involve too many people.

Get drafts out early and direct the discussions.

USe the people to review and not drive