Book a Demo

Author Topic: EA Application Development Process  (Read 3875 times)

Robert

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
EA Application Development Process
« on: February 17, 2003, 01:46:22 pm »
Dear all,

Analyzed and generated form availalbe resources, I got the general application process with EA by my own understanding.

1. Inception (Analysis and Basic design)
Tasks in this phase include determining use cases and actors.

2. Elaboration (Detail design)
Use cases have been fully detailed and accepted by the users, the class diagrams are complete when this phase is over. In other words, this phase is complete when the system is designed, reviewed, and ready for the developers to build it.

This phase is the detailing of the system requirements; the use case mode might require updating. As the follow of processing is detailed, Sequence and Collaboration diagrams help the flow. Class diagrams and some state diagrams should be created.

UI and test case design can be parallel process in this phase.

3. Construction (Coding)
Task in this phase include determining any remaining requirements, developing the software, and testing the software. No any new design decisions could be made because the software has been completely designed during elaboration phase. As code is completed, it should be reviewed by quality assurance to ensure that it meets design. If any new attribute are added, the new code should be updated back into EA model through reverse engineering.
(Issue: if component diagram should be created in this phase. Rational rose can generate skeletal code from it.)

More programmers could be added in if possible.

Construction is over when the software is complete and tested.

4. Transition
The transition phase is when the completed software product is turned over to the user. The tasks in this phase include completing the final accepting test, user documentation, preparing for user training. The Requirement specification, Use case diagrams, Class diagrams, Component diagrams, and deployment diagrams must be updated to reflect any final changes.

It is important to keep these models synchronized with the software product because the models will be used once the software product goes into maintenance mode.


I will listen to all advice from you all.

Thanks,

Robert Song
« Last Edit: February 17, 2003, 01:47:54 pm by Songxiangjun »

Tjerk

  • EA User
  • **
  • Posts: 231
  • Karma: +1/-0
    • View Profile
Re: EA Application Development Process
« Reply #1 on: February 18, 2003, 12:57:28 am »
Hi Robert,

EA is not restricting you in the process you use. If you would like to discuss processes and the appliance of UML in that mather, please look at the "UML Process" forum (see top level) for more discussions.

My opinion on your story is this: it's one possible way, but not the only way. Some processes might fit one problem, others another problem. The most important issues, in my opinion, are:
- using a general standard (see UML process forum) that the people involved understand and can work with;
- do not overdo a process or a standard, trim it down, but always have a good reason for trimming it down (not the other way around); Overdoing a process kills interest, enthousiasm and commitment of the people involved;
- Once a process and its deliverables have been chosen, take measures to ensure everybody sticks to the plan;

Greetings,
Tjerk

Robert

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Re: EA Application Development Process
« Reply #2 on: February 18, 2003, 10:44:05 am »
Hi Tjerk,

Yes, you are right. Which procee you use depends on situation. Over emphisis process could kill interest and efficiency.

Thanks for your help.

Robert