Download
1 / 11
110 likes | 265 Views
The B uff. President’s Weekly Letter Project. The B uffs. Chaklam Silpasuwanchai Software architect. Vilachith Phommasack System analyst. Watchara Sriswasdi Technical Manager. Tin Tin Aye Junior Programmer. Patra Thamavithya Project Manager. Agenda.
E N D
The Buff President’s Weekly Letter Project
The Buffs Chaklam Silpasuwanchai Software architect Vilachith Phommasack System analyst Watchara Sriswasdi Technical Manager Tin Tin Aye Junior Programmer Patra Thamavithya Project Manager
Agenda • Recent iteration and Progress • Plan for next iteration • Prototype demonstration
Current situation Mar 29 – Apr 10 Apr 19 - 28 C1 C2 I1 I2 E1 Construction Elaboration Inception
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
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
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
Meeting the Lifecycle Architecture milestone? • 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? • Risk is identified and mitigation strategy is determined • Requirement is quite stable • Bye Bye Elaboration phase!
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
Solution Flow Search task, issue, letter Import Word PWL Existed? Create Login No PWL Database Update/ Preview/ Delete Yes Email Publish Archive View
