Strana 1MBA kurz informačního inženýrství INITIATE CONSTRUCT DELIVER MAINTAIN & SUPORT quality assurance, manage project, trainig&education, manage people, manage risk, manage reuse, manage metrics, manage deliverables, manage infrastructure JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE MODEL TEST in the small GENERALIZE PROGRAM PROCESS TEST in the large RELEASE REWORK ASSESS SUPPORT identify defects and enhance- ments SOFTWARE DEVELOPMENT PROCESS

Strana 2MBA kurz informačního inženýrství SUPPORT PROCESSES FOR THE SOFTWARE DEVELOPMENT PROCESS RISK MANAGEMENT IDENTIFY A RISK ASSESS THE RISK DEVELOP MITIGATION STRATEGIES MITIGATE THE RISK REPORT RISK QUALITY ASSURANCE FOLLOW ISO STANDARDS TRAINING & EDUCATION DEVELOP A TRAINING PLAN REUSE MANAGEMENT COLLECT REUSABLE ITEMS METRICS MANAGEMENT DEVELOP METRICS PLAN DELIVERABLES MANAGEMENT INFRA- STRUCTURE MANAGEMENT MANAGE SOFTWARE CONFI- GURATION MANAGE SOFTWARE CONFI- GURATION APPLY CMM, … TECHNIQUES DEVELOP A RISK MANAGEMENT PLAN PERFORM INTRO TRAININGS PERFORM INTRO TRAININGS PERFORM DETAILED TRAININGS PERFORM DETAILED TRAININGS PERFORM AND DISCUSS

Strana 3MBA kurz informačního inženýrství JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management documents initial requirement project infrastructure project funding project charter potential roles during this phase: project manager analyst subject matter expert quality assurance engineer estimator / planner process specialist standards specialist tools specialist project sponsor JAD / meeting facilitator technical writer infrastructure engineer from maintain & support phase INITIATE PHASE The main goal is to lay the foundation for a successful project. This is hard due to pressures by senior management and developers to start “real work” as soon as possible.

Strana 4MBA kurz informačního inženýrství MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure project funding project charter potential roles during this phase: project manager software application documentation requirement allocation matrix models, source code management documents team leader software conf. manager test manager architectural modeler domain programmer subject matter expert quality assurance engineer domain modeler mentor infrastructure engineer technical writer component engineer reuse engineer test engineer proof-of-concept engineer from maintain & support phase CONSTRUCT PHASE The main goal of the construct phase is to build working software that is ready to be tested and delivered to its user community.

Strana 5MBA kurz informačního inženýrství TEST in the large RELEASE REWORK ASSESS packaged application documentation models and source code management documents requirement alloc. matrix potential roles during this phase: tested application documentation models requirement alloc. matrix project manager support manager operations manager training manager developer support engineer operations engineer trainer project auditor testing manager test engineer technical writer DELIVER PHASE The main goal here is to deploy the application, including the appropriate documentation, to the user community.

Strana 6MBA kurz informačního inženýrství potential roles during this phase: support manager support engineer operations manager operations engineer config. control board mgr. configuration item owner SUPPORT identify defects and enhance- ments tested application documentation models requirement alloc. matrix allocated maintenance changes to initiate or construct phase MAINTAIN & SUPPORT PHASE The goal here is to keep the application running in production and to ensure that changes to the application are well identified and acted on.

Strana 7MBA kurz informačního inženýrství DEFINE AND VALIDATE INITIAL REQUIREMENTS DEFINE SYSTEM FUNCTIONS vision commitment reasibility study existing applications maintenance changes DEFINE SYSTEM SCENARIOS CREATE MODELING CARDS HOLD SESSIONS INTERVIEW USERS PRIORITIZE REQUIRE- MENTS WALK THROUGH PROTOTYPES WALK THROUGH PROTOTYPES SIMULATE SCENARIOS DRAW PROCES MAPS requirement documentation (forms, tables, diagrams,...) project scope This is determining what needs to be built. Initial requirements are a foundation from which modeling can begin.

Strana 8MBA kurz informačního inženýrství DEFINE INITIAL MANAGEMENT DOCUMENTS DEFINE TASKS reasibility study project infrastructure initial requirements project objectives CREATE INITIAL SCHEDULE CREATE INITIAL RISK ASSESMENT CREATE INITIAL ESTIMATE CREATE INITIAL QUALITY ASSUR. PLAN DEFINE PROJECT SCOPE project plan risk assessment master test quality assurance plan Purpose of this process is to initiate documents such as the project plan and project risk assessment. They must be started at the beginning of the project and then maintained throughout its life.

Strana 9MBA kurz informačního inženýrství JUSTIFY IDENTIFY IMPLEMEN- TATION ALTERNATIVES vision estimate requirements documentation schedule risk assessment DETERMINE OPERATIONAL FEASIBILITY DETERMINE TECHNICAL FEASIBILITY DETERMINE ECONOMIC FEASIBILITY CHOOSE ALTERNATIVE IDENTIFY RISKS feasibility study recommendations project funding risk assessment The purpose is to determine whether or not an application should be built. It is a reality check to determine whether or not a project makes a sense.

Strana 10MBA kurz informačního inženýrství DEFINE INFRASTRUCTURE SELECT TOOLS project plan initial requirements feasibility study existing infrastructure DEFINE TEAM SELECT STANDARDS AND GUIDELINES SELECT METHODO- LOGY NEGOTIATE DELIVE- RABLES GREATE GROUP KNOWLEDGE BASE team definition (profile, skill database,...) tools selection tailored software process group knowledges The project infrastructure is made up of the project team, the tools that they will use, and a tailored version of the software development process that the team will follow.

Strana 11MBA kurz informačního inženýrství MODEL ARCHITECTU- RAL MODELING requirement documentation modeling standards TECHNICAL MODELING HUMAN INTERACTION DOMAIN MODELING PROBLEM DOMAIN MODELING MANAGE METRICS TASK MODELING models (diagrams, docs) test plan requirement alloc. matrix The developers first need to understand what the are supposed to build. This “software analysis and design” process should be performed iteratively, because of developers do not need to do all of the analysis first time, then do all of the design and then all of the coding.

Strana 12MBA kurz informačního inženýrství PROGRAM PROCESS UNDERSTAND MODELS models project infrastructure MAKE SOURCE CODE PREPARE PROJECT INTEGRATION PLAN PREPARE CODE FOR INSPECTIONS INTEGRATE AND PACKAGE INTEGRATE AND PACKAGE SYNCHRONIZE SOURCE CODE WITH MODELS packaged application source code software components OPTIMIZE CODE BUILD SOFTWARE APPLICATION REUSE EXISTING CODE AND COMPONENTS DOCUMENT SOFTWARE APPLICATION DOCUMENT SOURCE CODE PERFORM METRICS During this process the source code is written, documented, reviewed, tested and packaged for delivery. For this to be successful, the models must drive the development of the source code. This process is far more to writing source code of programs.

Strana 13MBA kurz informačního inženýrství GENERALIZE IDENTIFY POTENTIAL REUSABLE ITEMS project deliverables HOLD GENERALIZA- TION SESSIONS RELEASE MAKE DOCUMENTA- TION PERFORM METRICS REFACTOR CODE reusable items This is the recognition that the short-term pressures of software development result in the temptation for developers to settle for specific, non-reusable solutions. In this process, application specific items are identified and then reworked to be reusable by other development teams.

Strana 14MBA kurz informačního inženýrství TEST IN THE SMALL DEVELOP TEST PLAN DEVELOP TEST PLAN models source code requirements master test quality assurance plan SCENARIO AND PROCESS TEST RECORD DEFECTS WALK- THROUGH MODELS WALK- THROUGH MODELS USER INTERFACE TESTING PROGRAM CODE TESTING PROGRAM CODE TESTING REVIEW TECHNICAL DESIGN INSPECT SOURCE CODE REVIEW PROTOTYPES tested artifacts test results master test quality assurance plan This process focuses on the verification, validation, and testing of documents, models, and source code produced. In many ways it is quality assurance techniques such as peer reviews and inspections combined with unit testing techniques for validating code.

Strana 15MBA kurz informačního inženýrství TEST IN THE LARGE ACCEPT TEST PLAN packaged application master test quality assurance plan previous test results FUNCTION TEST OPERATIONS TEST STRESS TEST ALPHA/BETA TEST INSTALLATION TEST tested application test results PERFORM METRICS USER ACCEPTANCE TEST RECORD DEFECTS The goal here is to ensure that the application works on its entirety. This includes user testing in which the application is specifically tested by members of user community.

Strana 16MBA kurz informačního inženýrství REWORK PRIORITIZE DEFECTS tested application tested results, documents models, source code requirement alloc. matrix organizational priorities REMODEL TEST IN THE SMALL UPDATE DOCUMENTA- TION PERFORM METRICS REPROGRAM reworked application models, source code documentation requirement alloc. matrix The focus of this process is to fix the critical defects discovered by the “test in the large” process to ensure the successful deployment of the application. It is like a miniature version of the “construct” process.

Strana 17MBA kurz informačního inženýrství RELEASE ACCEPT TRAINING AND RELEASE PLANS release procedures training plans application package operations and support documentation ACCEPT USER SUPPORT AND OPERATIONS DOCUMENTS DEPLOY THE OPERATION PROCESS FINALIZE CONVERSION OF LEGACY DATA DEPLOY THE SUPPORT PROCESS TRAIN OPERATIONS STAFF ANNONCE ACTUAL RELEASE TO USERS TRAIN SUPPORT STAFF PACKAGE APPLICATION released application procedures documentation TRAIN USERS PERFORM METRICS DEPLOY THE APPLICATION The goal of this process is to deploy the application and its corresponding documentation successfully to the user community (end users and also operations department staff that will help the users work with the application effectively).

Strana 18MBA kurz informačního inženýrství ASSESS project deliverables project metrics group knowledge base REVIEW PROJECT DELIVERA- BLES ASSESS TEAM MEMBER PERFORMANCE DEVELOP LEARNING HISTORY DEVELOP PROJECT ASSESSMENT learning history project and staff assessment process improvement plan ANALYZE METRICS DEVELOP STAFF ASSESSMENT ASSESS USER INVOLVEMENT DEVELOP SOFTWARE PROCESS IMPROV. PLAN This process has two goals: a) for the project team, to learn from its experiences developing the application b) to provide an opportunity to evaluate the members of the project team to support their personal growth

Strana 19MBA kurz informačního inženýrství SUPPORT RESPOND TO REQUEST support requests DETERMINE SOLUTION IDENTIFY HW AND SW UPGRADES IDENTIFY TRAINING PLAN RECORD SOFTWARE CHANGE REQUESTS PROVIDE RESOLVE INFORMATION solution software change requests The objective of this process is to respond to incoming support requests from users, to identify a resolution for the request, and then to oversee the implementation of that resolution. This is performed on a continual, daily basis way.

Strana 20MBA kurz informačního inženýrství IDENTIFY DEFECTS AND ENHANCEMENTS ANALYSE SOFTWARE CHANGE REQUESTS software change requests models requirement alloc. matrix documentation release schedule PRIORITIZE MAINTENANCE CHANGES ALLOCATE MAINTENANCE CHANGES TO CONF. ITEMS allocated maintenance changes The purpose of this process is to analyze software change requests defined during the “support” process so that maintenance changes to the application may be identified and allocated to the appropriate configuration items. This manages basic change control issues and identifies requirements for future releases of the application.