Specifying e-Gov Software

1. Specifying e-Gov Software Slamet Santoso Microsoft Developer Network (MSDN) Regional Director Indonesia Chief Operating Officer (COO) PT. Puspa Intimedia Internusa ( www.intimedia.com ) slamet@intimedia.com

2. Agenda • Introduction • Software in E-Gov initiative • Considerations to specify e-Gov software • Buy or build decision? • Steps to build and implement e-Gov software • Managing e-Gov project

3. Introduction • E-Gov is a need or a must • Integrated and comprehensive e-Gov • Planning & Designing e-Gov • Considerations and management of e-Gov

4. Software supporting e-Gov • E-Gov is a system that integrates components • Hardware or infrastructure • Software • Data & information • Personnel • Rules & operational procedures • Software in a very important position

5. Considerations to specify the software • Starting from the scopes & functionalities • Software features & functionalities fitting to business requirement • Technical factors • Economical factors • Operational factors

6. Starting from the scopes & functionalities • What are the goals / objectives? • What are the scopes? • What are the functionalities? • What are the features? • What are the constraints? • What we plan and design? Blueprints of e-Gov

7. Software features & functionalities E-Gov requirements Software features & functionalities fitting to business requirement Business process mapping or Business process reengineering

8. Software E-Gov • Portal and Content Management • Workflow Engine • Mail Service • User Management • Interface to • Back end system • GIS User management Portal Content Management Service Workflow Engine Mail service Back end system

9. Portal • Features • Contents (news, events,…) • Documents sharing • Forums management • Chatting • Mail integration • Directory management • impersonation • Channels management • etc

10. Technical Factors • Performance • Ease of use • Reliability & Availability • Maintainability • Scalability • Security • Connectivity • Accessibility

11. Performance • Correctness & Accuracy • Speed • Capacity

12. Ease of use • Simple to use • Nice user interface • Personalization 

13. Reliability & Availability • Reliability is a measure that system successfully functions • Reliable system tends to be highly available • Dependent to system capacity to handle transactions or user access system ?

14. Maintainability • Ease to maintain or modify if • Requiring extension • Requiring correction • Requiring integration to others • Dependent on how system was designed Is it easy to correct the code ? Is it easy to add the code ? Is it easy to integrate the code ?

15. Scalability • Ease to scale out and scale up when enhancing system capacity • Dependent on how system was designed • Possible to deploy software on a farm of server machines • High availability • Process server • Data server 100 users 10 G Data 1 server >>10 G Data >1 Server >>100 users

16. Security • Not authorized user can not log in a secure system through any mechanisms • OS layer • Database layer • Application layer • Secure system anticipate any actions to make the system not secure • Secure system • User management • Cryptography system Not authorized Encrypted data Other system Authorized

17. Connectivity • Ease to connect to other external system • Connectivity  connection or interface to • Database • Process • Hardware external database system External process

18. Accessibility • Ease to access it from client’s devices • Desktop computers • Pocket PC or PDA • Hand phone and smart phone system PDA Smart phone

19. Economical Factors • Total Cost of Ownership • Cost of development or procurement • Cost of implementation • Cost of maintenance • Corrective • Adaptive • Anticipative

20. Operational Factors • Supports from vendor • Operations framework • Disaster Recovery • Back up • Recovery

21. When buy? Software features fitting to e-gov requirement Short time to delivery Customizable Connectivity Good support from vendor Cost When build? Many specific requirements and integrations to legacy system Long time to delivery Cost Buy or build decision

22. Steps to build and implement the software • Envisioning • Planning • Developing • Stabilizing • Deploying • Maintaining

23. Managing e-Gov Project • Using • Good process methodology • Good resources & team model • Good tools & technology • Good risk management

24. Why Software Project Management ? • The project has limited resources • The project has some different characteristics • The project is very dynamics • The deliverables are not physical goods • The metrics is not as clear as others • Size, scope • quality

25. Key Issues • Software Projects • How should we make estimation (size, effort, cost) • How can we manage • The project scopes (size) and user expectations • The project goals • The requirement changes • The project risks • How should the project trade-off be performed

26. Project Trade-Off

27. PM and Soft. Dev. Methodology • Project Management • Body of Knowledge • (PMBOK) - Areas • - Managing scope • - Managing processes • - Managing resources & team • - Managing risks • Managing qualities • Managing changes • Managing communication, etc • Project Management • Body of Knowledge (PMBOK) - Processes • Initiating • Planning • Executing & Controlling • Closing • Standards & Frameworks • IEEE process standard • CMM • ISO • MSF • RUP Software Development Methodology Software Project Management Software Dev. Paradigms - Classic life cycle - Iterative - Prototyping - Spiral - Rapid Application Development

28. PHASES Envisioning Planning Developing Stabilizing Deploying ACTIVITIES Business Modeling & Requirement Analysis & Design Coding Test Deployment Phases and Activities

29. Team Model

30. Risk Management Process

31. Q & A