Chapter 17 - Formulación y Planeación para Ingeniería Web

Software Engineering: A Practitioners Approach, 6/e
Chapter 17 Formulation and Planning

for
Web Engineering
copyright 1996, 2001, 2005
R.S. Pressman & Associates, Inc.

For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
Formulation

begins with the identification of business need moves into a description of WebApp objectives defines major features and functions establishes a requirements gathering activity that will lead to the development of an analysis model allows stakeholders and the web engineering team to establish a common set of goals and objectives for the construction of the WebApp.

identifies the scope of the development effort provides a means for determining a successful, outcome..
Formulation Questions
What is the main motivation (business need) for the WebApp? What are the objectives that the WebApp must fulfill? Who will use the WebApp? Answers provide Informational goalsindicate an intention to provide specific content and/or information for the end-user Applicative goalsindicate the ability to perform some task within the WebApp
WebE Requirements Gathering
Ask stakeholders to define user categories and develop descriptions for each category Communicate with stakeholders to define basic WebApp requirements Analyze information gathered and use information to follow-up with stakeholders Define use-cases (Chapter 8) that describe interaction scenarios for each user class
Defining User Categories
What is the users overall objective when using the WebApp? What is the users background and sophistication relative to the content and functionality of the WebApp? How will the use arrive at the WebApp? What generic WebApp characteristics does the user like/dislike?
Communicating with Stakeholders
Traditional focus groupsa trained moderator meets with a small group of representative end-users (or internal stakeholders playing the role of endusers). Electronic focus groupsa moderated electronic discussion conducted with a group of representative end-users and stakeholders. Iterative surveysa series of brief surveys, addressed to representative users and requesting answers to specific questions about the WebApp Exploratory surveysa Web-based survey that is tied to one or more WebApps that have users who are similar to the ones that will use the WebApp to be developed. Scenario-buildingselected user are asked to create informal use-cases that describe specific interactions with the WebApp.
Preliminary Analysis

Categorize information gathered by user class and transaction type Develop lists of

content objects operations that are applied to content objects within a specific user transaction functions (e.g., informational, computational, logical, and helporiented) that the WebApp provides for end-users other non-functional requirements that are noted during the communication activities.
Use-Cases
Provide the detail necessary to create an effective analysis model Help the developer to understand how users perceive their interaction with the WebApp Use-cases help to compartmentalize Web engineering work Use-cases provide important guidance for those who must test the WebApp
The WebE Team
WebE team roles
Content Developer/Providers Web Publisher Web Engineer. Business domain experts Support Specialist Administrator (a.k.a. Web Master)
Project Differences
Traditional Projects Requirements Gathering Technical Specifications Project Duration Testing and QA Risk Management Half-life of deliverables Release Process Post-release customer feedback Rigorous Robust: models, spec Measured in months or years Focused on achieving quality targets Explicit 18 months or longer Rigorous Requires proactive effort small e-Projects Limited Descriptive overview Measured in days, weeks or months Focused on risk control Inherent 3 to 6 months or shorter Expedited Automatically obtained from user interaction major e-Projects Rigorous robust: UML models, spec Measured in months or years SQA as described in Chapter 26 Explicit 6 to 12 months or shorter Rigorous Obtained both auto matically and via solicited feedback
10
Outsourcing vs. In-house

support specialist s Web engineers support specialist s Cont ent dev elopers administ rat or administ rat or out sourcing v endor Web publisher business managers st akeholders business managers st akeholders Web publisher Web engineers v endor liaison
Cont ent dev elopers
end-users
market ing & sales
end-users
market ing & sales
(a) in-house development
(a) out sourced development
11
WebApp Outsourcing - I
Initiate the project by performing the following tasks internally
Gather requirements Develop a rough design Develop a rough schedule with delivery dates
Consider increments For in-house staff For outsourcing vendor
Make a list of responsibilities

Define liaison mechanisms
12
WebApp Outsourcing - II

Select Candidate Outsourcing Vendors Assess the Validity of Price Quotes and the Reliability of Estimates
Does the quoted cost of the WebApp provide a direct or indirect returnon-investment that justifies the project? Does the vendor that has provided the quote exhibit the professionalism and experience we require?
Understand the Degree of Project Management You Can Expect/Perform Assess the Development Schedule Manage Scope
13
WebApp Planning - In-House
Understand scope, the dimensions of change, and project constraints Define an incremental project strategy Perform risk analysis Develop a quick estimate Select a task set (process description) Establish a schedule Define project tracking mechanisms Establish a change management approach
14
WebE Worst Practices
We have a great idea, so lets begin building the WebAppnow. Stuff will change constantly, so theres no point in trying to understand WebApp requirements. Developers whose dominant experience has been in traditional software development can develop WebApps immediately. No new training is required. Be bureaucratic. Testing? Why bother?
15

Chapter 17 - Formulación y Planeación para Ingeniería Web

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Chapter 17 - Formulación y Planeación para Ingeniería Web

Caricato da

Copyright:

Formati disponibili

Software Engineering: A Practitioners Approach, 6/e

Chapter 17 Formulation and Planning

R.S. Pressman & Associates, Inc.

WebE Requirements Gathering

Defining User Categories

Communicating with Stakeholders

The WebE Team

WebE team roles

Outsourcing vs. In-house

Cont ent dev elopers

market ing & sales

market ing & sales

(a) in-house development

(a) out sourced development

Initiate the project by performing the following tasks internally

Consider increments For in-house staff For outsourcing vendor

Make a list of responsibilities

Define liaison mechanisms

WebApp Planning - In-House

WebE Worst Practices

Potrebbero piacerti anche