1 / 15

Web Development Process Description

Web Development Process Description. A process for Web Development projects. WebDev Process. Approved Project Proposal. Approved Design Direction. Accepted Solution. Request Solution. 1.0 Initiate Project. 2.0 Design Solution. 4.0 Develop Components. 5.0 Test Iteration.

stacia
Télécharger la présentation

Web Development Process Description

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Development Process Description A process for Web Development projects

  2. WebDev Process Approved Project Proposal Approved Design Direction Accepted Solution Request Solution 1.0 Initiate Project 2.0 Design Solution 4.0 Develop Components 5.0 Test Iteration 6.0 Launch Solution 3.0 Prepare Infrastructure Maintain Solution Notes: “Prepare Infrastructure” includes planning and process development for change control, content workflow, testing, piloting, business transition, user training, user support, marketing, maintenance, and creating technical infrastructure. “Component” includes all types of content (e.g. features, functions, modules, web pages, applications, calculators, etc.) Legend: Preceding or Succeeding Process Project Process Concurrent Development Milestone

  3. Name Purpose WebDev Process • Develop a web-based solution that satisfies the strategic objectives, while conforming to the quality expectations of stakeholder groups. Input Activities Output • Request to develop a web-based solution; the request may occur in various forms: • Formal or informal • Verbal or written • Initial project charter • Initial creative brief • Initial prototype • 1.0 Initiate Project • Clarify scope, objectives, and boundaries of the project. • Obtain management approval and commitment to proceed with the project. • 2.0 Design Solution • Obtain approval for initial design direction. • Then through an iterative process, establish requirements and specify design. • 3.0 Prepare Infrastructure • Prepare the technical and process infrastructure to support design, development, testing, launch, and maintenance of the solution. • 4.0 Develop Components • Perform concurrent development of multiple components, prepare for iteration testing, and provide feedback to help refine requirements and design. • 5.0 Test Iteration • Verify the iteration conforms to requirements and design specifications. • Determine when solution is complete, ready for launch. • 6.0 Launch Solution • Launch the solution -- first to a “pilot” set of users, then to all users. • Conclude the project. • Web-based solution • In production • Generally available • Supported • Maintained • Project documentation artifacts: • Project Charter • Creative Brief • Project Plan • Requirements List • Design Specification Deliverables • Infrastructure Diagram • Supporting plans • Test results Notes • “Component” includes all types of content (e.g. features, functions, modules, web pages, applications, calculators, etc.) “Prepare Infrastructure” includes planning and process development for change control, content workflow, testing, piloting, business transition, user training, user support, marketing, maintenance, and creating technical infrastructure.

  4. 1.0 Initiate Project Request Solution 1.1 Determine Business Objectives Approved Project Proposal 1.2 Identify Stakeholders • 1.6 Prepare Project Proposal • Project Charter • Creative Brief • Site Map Concept • Project Plan 1.3 Develop User Profiles 1.7 Hold Kickoff Meeting 1.4 Explore Technology Options 1.5 Determine Project Approach 2.0 Design Solution 3.0 Prepare Infrastructure

  5. Name Purpose 1.0 Initiate Project • Clarify scope, objectives, and boundaries of the project. • Obtain management approval and commitment to proceed with the project. Input Activities Output • Request to develop a (web-based) solution; the request may occur in various forms: • Formal or informal • Verbal or written • Initial project charter • Initial creative brief • Initial prototype EXTERNAL DRIVERS: • Changing Business • Marketplace • Technology • Competition • 1.1 Determine business objectives • Become familiar with the business context. • State the success criteria from a business perspective. • Relate this web project to the overall business and web strategy. • 1.2 Identify Stakeholders • Identify the sponsor, and the project team members. • Determine roles and responsibilities of each stakeholder. • 1.3 Develop User Profiles • Identify users. • Understand the users and how to communicate with them through the web site. • 1.4 Explore Technology Options • Consider the possible technology approaches to building the web site. • Prioritize architecture quality attributes. • Prepare context diagram. • Begin defining environment needs. • 1.5 Determine Project Approach • Determine how to apply the WebDev process to this project. • Modify the WebDev Process description for this project. • 1.6 Prepare Project Proposal • Prepare project proposal (see list under “Output”). • Obtain required management approval and commitment. • 1.7 Hold Kickoff Meeting • Project proposal : • Project Charter • Creative Brief • Site Map Concept • Project Plan • Project Charter includes: • Business strategy • Context Diagram • Objectives, Scope • Stakeholders • Constraints • Assumptions • Risk • Cost/Benefit Analysis • Priorities • Quality Standards • Project Plan includes: • Schedule • Organizational chart • Staffing plan • Equipment plan Notes • FSDM: corresponds to module PPI “Creative Brief” refers to a document that describes the user experience with the web-based solution. It discusses the look and feel objectives, and how this fits with the overall web strategy and business objectives.

  6. 2.0 Design Solution 1.0 Initiate Project Approved Design Direction • 2.2 Establish Solution • Requirements • Functional • Performance • Security • Legal and Compliance • Technology • Applicable Standards • 2.3 Specify • Solution Design • Prototypes • Technology Selection • System Delivery Specification • Site Map • Navigation Scheme • Web Names and Tags 2.1 Explore Design Options 3.0 Prepare Infrastructure 4.0 Develop Components 5.0 Test Iteration 2.5 Approve and Communicate Changes 2.4 Update Project Plan 3.0 Prepare Infrastructure 4.0 Develop Components

  7. Name Purpose 2.0 Design Solution • Obtain approval for initial design direction. • Then through an iterative process, establish solution requirements and specify solution design. Input Activities Output • Project Charter • Creative Brief • Site Map Concept • Project Plan • Design Issues • Test Results • Prototyping Environment • Software Configuration Management (SCM) system EXTERNAL DRIVERS: • Changing Business • Marketplace • Technology • Competition • 2.1 Explore Design Options • Brainstorm; construct models; narrow ideas down. • Consider user interface design as well as overall architecture to support solution. • Obtain management approval for design direction. • 2.2 Establish Solution Requirements • Define user scenarios. • Prepare requirements list (see list under “Output”). • Consider feedback from infrastructure preparation, component development, and iteration testing. • Refine requirements through review of design specification deliverables. • 2.3 Specify Solution Design • Prepare design specification deliverables (see list under “Output”). • Consider feedback from infrastructure preparation, component development, and iteration testing. • Refine design through review of the approved requirements list • Demonstrate prototypes; test usability and performance. • 2.4 Update Project Plan • Update plan based on requirements list and design specification deliverables. • Plan the next round of infrastructure preparation, component development, and iteration testing. • 2.5 Approve and Communicate Changes • Utilize the SCM system to save current version of deliverables. • Inform stakeholders of any requirement or design changes that may impact them. • User Scenarios • Requirements List: • Functionality • Performance • Security • Legal and Compliance • Technology • Applicable Standards • Design Spec Deliverables: • Prototypes • Technology Selection • System Delivery Spec • Site Map • Navigation Scheme • Web Names and Tags • Updated Project Plan • Usability and performance test results Notes • FSDM: corresponds to modules SRA, SDS, AIP

  8. 3.0 Prepare Infrastructure 1.0 Initiate Project 2.0 Design Solution 4.0 Develop Components 5.0 Test Iteration • 3.1 Diagram Technical • Infrastructure • Prototyping Environment • Development Environment • Test Environment • Staging Environment • Production Environment • Network, IP Addresses • Firewalls, Domain Names • Web Servers • Application Servers • Database Servers • Fail-over Servers • Statistics • Monitoring System 3.2 Obtain Hardware and Software 3.3 Install, Configure, and Validate 2.0 Design Solution 4.0 Develop Components 5.0 Test Iteration 6.0 Launch Solution • 3.4 Plan and Develop Supporting Processes • Change Control • Content Workflow • Testing • Solution Pilot • Business Transition • User Training • User Support • Marketing • Maintenance • 3.5 Update Supporting Systems • Defect Tracking System • Software Configuration Management System

  9. Name Purpose 3.0 Prepare Infrastructure • Prepare the technical and process infrastructure to support design, development, testing, launch, and maintenance of the solution. Input Activities Output • Project Charter • Creative Brief • Project Plan • User Scenarios • Requirements List • Design Spec Deliverables • Updated Project Plan • Infrastructure Issues • Test Results • ASSUMPTION: • Infrastructure components for this project are assumed available as commercial off-the-shelf or Company off-the-shelf. If needed, utilize “2.0 Design Solution” and “4.0 Develop Components” to design and develop additional infrastructure. • 3.1 Diagram Technical Infrastructure: • Prototyping Environment • Development Environment • Test Environment • Staging Environment • Production Environment • Network, IP Addresses • Firewalls, Domain Names • Web Servers • Application Servers • Database Servers • Fail-over Servers • Statistics • Monitoring system • 3.2 Obtain Hardware and Software • Compare project requirements with internal Company resources. • Purchase hardware and software from external vendor or allocate from internal Company resources. • 3.3 Install, Configure, and Validate • Prepare technical infrastructure. • 3.4 Plan and Develop Supporting Processes: • Change Control • Content Workflow • Testing • Solution Pilot • Business Transition • User Training • User Support • Marketing • Maintenance • 3.5 Update Supporting Systems: • Defect tracking system • Software Configuration Management (SCM) system • Prototyping environment • Development environment • Test environment • Staging environment • Production environment • Infrastructure Diagram • Supporting plans and processes: • Change Control • Content Workflow • Testing • Solution Pilot • Business Transition • User Training • User Support • Marketing • Maintenance • Supporting Systems • Defect Tracking • SCM Notes • FSDM: corresponds to modules AIP, UPD, PER, PAI, PSD “Prepare Infrastructure” includes planning and process development for change control, content workflow, testing, piloting, business transition, user training, user support, marketing, maintenance, and creating technical infrastructure.

  10. 4.0 Develop Components 2.0 Design Solution 3.0 Prepare Infrastructure Component N 4.3 Identify Design or Infrastructure Issues Component 2 Component 1 • 4.2 Perform Development • Analyze • Design • Code and Build • Unit Test • Integration Test 4.1 Plan for Iteration 4.5 Build And Release 4.4 Prepare for Iteration Testing “Component” includes all types of content (e.g. features, functions, modules, web pages, applications, calculators, etc.) 5.0 Test Iteration

  11. Name Purpose 4.0 Develop Components • Perform concurrent development of multiple components, prepare for iteration testing, and provide feedback to help refine requirements and design. Input Activities Output • Development environment • SCM system • Content Work Flow Process • User Scenarios • Requirements List • Test Strategy • Design Specification Deliverables: • Application Prototype • Technology Selection • System Delivery Spec • Site Map • Navigation Scheme • Web Names and Tags • 4.1 Plan for Iteration • Identify, prioritize, and allocate tasks; identify task dependencies • Determine dependencies between components, develop integration plan • 4.2 Perform Development • Analyze -- Decide what to build. • Design -- Decide how to build it. • Code and Build -- Build it. • Unit test -- Verify correctness of unit of work. • Integration test -- Verify unit works with other components. • 4.3 Identify Design or Infrastructure Issues • Identify issues that require resolution through design or infrastructure changes. • 4.4 Prepare for Iteration Testing • Create or update the test plan, test cases, and test data necessary to support iteration testing. • Validate test environment to ensure readiness for iteration build and release. • 4.5 Build and Release • Develop build scripts, build debug and preliminary test releases, move to development and test environments • Create final build, release the solution, and move to test environment • Design Issues • Infrastructure Issues • Test Iteration Preparation: • Test Plan • Test Cases • Test Data • Set of components • Conforming to requirements and design specifications • Ready for iteration testing Notes • FSDM: corresponds to modules TSD, TPD • “Component” includes all types of content (e.g. features, functions, modules, web pages, applications, calculators, etc.)

  12. 5.0 Test Iteration 3.0 Prepare Infrastructure 4.0 Develop Components 2.0 Design Solution 3.0 Prepare Infrastructure 4.0 Develop Components • 5.1 Perform • System Tests* • Functionality • Content • Links • Browsers • Security • Legal and Compliance • External Systems • Performance • Stress • Load Balancing • Scalability • Fail-over 5.3 Evaluate Test Results Accepted Solution 5.4 Perform Acceptance Review • 5.2 Perform User • Acceptance Tests* • Solicit Customer Feedback • Usability Testing • Alpha Testing • Beta Testing 6.0 Launch Solution * Tests performed during iteration are dependent on what components are developed to date.

  13. Name Purpose 5.0 Test Iteration • Verify the iteration conforms to requirements and design specifications. • Determine when solution is complete, ready for launch. Input Activities Output • Set of components • Conforming to requirements and design specifications • Ready for iteration testing • User Scenarios • Requirements List • Design Specification Deliverables • Test Environment • Test Strategy • Test Iteration Preparation: • Test Plan • Test Cases • Test Data • 5.1 Perform System Tests • Functionality • Content • Links • Browsers • Security • Legal and Compliance • External Systems • Performance • Stress • Load Balancing • Scalability • Fail-over • 5.2 Perform User Acceptance Tests • Solicit customer feedback. • Usability Testing • Alpha Testing • Beta Testing • 5.3 Evaluate Test Results • Compare current iteration to requirements and design specifications. • Determine whether content is complete, ready for final acceptance review. • 5.4 Perform Acceptance Review • Obtain stakeholder approval to launch the solution. • System testing results • User acceptance testing results • Solution, approved for launch Notes • FSDM: corresponds to module SAT • Tests performed during iteration are dependent on what components are developed to date; more extensive testing occurs with later iterations.

  14. 6.0 Launch Solution 5.0 Test Iteration 6.1 Finalize Production System 3.0 Prepare Infrastructure 6.2 Implement User Training Plan 6.3 Implement User Support Plan 6.6 Conduct Solution Pilot 6.4 Implement Business Transition Plan 6.9 Conclude Project 6.5 Implement Maintenance Plan 6.7 Implement Marketing Plan 6.8 Announce General Availability Maintain Solution

  15. Name Purpose 6.0 Launch Solution • Launch the solution -- first to a “pilot” set of users, then to all users. • Conclude the project. Input Activities Output • Solution, approved for launch • Production environment • Supporting plans • Change Control • Content Workflow • Solution Pilot • Business Transition • User Training • User Support • Marketing • Maintenance • 6.1 Finalize Production System • Move release to production environment • Enable monitoring, backup, and fail-over systems in production system. • 6.2 Implement User Training Plan • Provide necessary training for users. • 6.3 Implement User Support Plan • Update desktop software, if needed. • 6.4 Implement Business Transition Plan • Implement changes to the business processes to accommodate launch of solution. • 6.5 Implement Maintenance Plan • Implement the plan to ensure the on-going maintenance of solution. • 6.6 Conduct Solution Pilot • Release the solution to a limited number of users. • 6.7 Implement Marketing Plan • Notify users via E-Mail, print, TV, Radio, etc.. • 6.8 Announce General Availability • Notify search Engines. • 6.9 Conclude Project • Celebrate launch of solution. • Review launched solution, and prepare final project report. • Web-based solution • In production • Generally available • Supported • Maintained • Final project report Notes • FSDM: corresponds to module TRA

More Related