1. The B uff

2. The Buffs

3. Agenda 1. Recent iteration and Progress 2. Plan for next iteration 3. Prototype demonstration

4. I1 I2 E1 C1 C2 Current situation Inception Elaboration Construction Mar 29 – Apr 10 Apr 19 - 28

5. Progress on the Elaboration iteration 1  Held a structured confirmation interview with Ms. Izel  Yes/No question  Refined the requirements and related documents  Determine the exact development and management tool  PHP Framework: Code igniter  Google code for version controlling, issue tracking, task allocation, and knowledge distribution using built-in wiki  Project schedule monitoring through Gantt chart  Rational Rose for generating UML diagrams  Define the overall architecture based on the most significant use cases and an assessment of risk  The selected PHP framework kind of base lining the architecture for us which is nice  Persistence pattern using Data Mapper.  Model view controller pattern

6. Progress on the Elaboration iteration 1(cont.)  Risk Management  Risk and the corresponding mitigation/contingency strategy is identified  Documented in the Risk List and Risk Management Plan  Perform object oriented design and analysis on critical use cases (~70%)  Static and dynamic diagram  Documented in the SAD doc and Use case realization doc  Prototypes  Digital prototype for group understanding  Working (not thrown away) prototype for getting rapid customer feedback  ~15% use cases  Iteration plan for next iteration

7. Problem encountered in this iteration  We have no user involvement in this iteration at all  More frequent short meeting  Cost and benefit is mostly intangible and difficult to measure.  Eg. Customer satisfaction  Must find a way  Documentation becomes a big overhead  we lack experiences in customizing the RUP framework, anyhow, we are getting better  Frankly saying, some documents are never opened again once it’s finished?  We do not work exactly according the Gantt chart  We need to keep up with the schedule  Some risk is not properly mitigated and occurs. Eg. Schedule slip  Minor conflicts on SVN lost updates

8. Meeting the Lifecycle Architecture milestone? 1. Since most of the baseline architecture for web application is quite determined by the framework solution, we have a easier life.  Main use cases are tested.  Selection and verification? 2. Risk is identified and mitigation strategy is determined 3. Requirement is quite stable 4. Bye Bye Elaboration phase!

9. Construction iteration 1 Gantt Chart

10. Plan for Construction iteration 1(April 12)  Refine documentation accordingly  Refine analysis and design diagrams  Describing the remaining use cases and fill in design  Implement the rest of the use cases  Some extreme programming practices may be applied eg. Continuous integration  Integration test and functional test  Hopefully, we plan to release the beta version by next iteration  Get customer feedback  Prepare the beta deployment  Contact the IT-serv

11. Solution Flow Login Create Update/ Preview/ Delete Publish PWL Existed ? No Yes Email Archive PWL Database Search task, issue, letter View Import Word