chapter 17 - formulación y planeación para ingeniería web
TRANSCRIPT
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
1/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
Software Engineering: A Practitioners Approach, 6/e
Chapter 17Formulation and Planning
for
Web Engineeringcopyright 1996, 2001, 2005
R.S. Pressman & Associates, Inc.
For University Use Only
May be reproduced ONLY for student use at the university levelwhen used in conjunction with Software Engineering: A Practitioner's Approach.
Any other reproduction or use is expressly prohibited.
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
2/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith 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..
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
3/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
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 contentand/or information for the end-user
Applicative goalsindicate the ability to perform some task within
the WebApp
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
4/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
WebE Requirements Gathering
Ask stakeholders to define user categories and developdescriptions for each category
Communicate with stakeholders to define basic WebApp
requirements
Analyze information gathered and use information tofollow-up with stakeholders
Define use-cases (Chapter 8) that describe interaction
scenarios for each user class
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
5/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
Defining User Categories
What is the users overall objective when using theWebApp?
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?
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
6/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
Communicating with Stakeholders
Traditional focus groupsa trained moderator meets with a small group of
representative end-users (or internal stakeholders playing the role of end-users).
Electronic focus groupsa moderated electronic discussion conducted witha group of representative end-users and stakeholders.
Iterative surveysa series of brief surveys, addressed to representativeusers and requesting answers to specific questions about the WebApp
Exploratory surveysa Web-based survey that is tied to one or moreWebApps that have users who are similar to the ones that will use theWebApp to be developed.
Scenario-buildingselected user are asked to create informal use-casesthat describe specific interactions with the WebApp.
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
7/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
Preliminary Analysis
Categorize information gathered by user class andtransaction type
Develop lists of
content objects
operations that are applied to content objects within a specificuser transaction
functions (e.g., informational, computational, logical, and help-oriented) that the WebApp provides for end-users
other non-functional requirements that are noted during thecommunication activities.
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
8/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
Use-Cases
Provide the detail necessary to create an effectiveanalysis model
Help the developer to understand how users perceive
their interaction with the WebApp
Use-cases help to compartmentalize Web engineeringwork
Use-cases provide important guidance for those who
must test the WebApp
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
9/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
The WebE Team
WebE team roles Content Developer/Providers
Web Publisher
Web Engineer.
Business domain experts Support Specialist
Administrator (a.k.a. Web Master)
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
10/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005 1
Project Differences
Traditional Projects small e-Projects
Requirements
Gathering
Rigorous Limited
TechnicalSpecifications
Robust: models, spec Descriptive overview
Project Duration Measured in months oryears
Measured in days,weeks or month s
Testing and QA Focused on achievingquality tar-
gets
Focused on risk control
Risk Management Explicit Inherent
Half-life ofdeliverables
18 months or longer 3 to 6 months or shorter
Release Process Rigorous Expedited
Post-release customerfeedback
Requir es proactiveeffort
Automaticallyobtained from userinteraction
major e-Projects
robust: UML mode ls,spec
Measured inmonths or years
SQA as d escribedin Chapter 26
Explicit
Rigorous
6 to 12 month sor shorter
Rigorous
Obtained both auto-matically and viasolicited feedback
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
11/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005 1
Outsourcing vs. In-house
We b
engineers
Cont ent
developers
We b
publisher
stakeholders
end-users
marketing
&
sales
support
specialist s
administ rat or
business
managers
(a) in-house development
stakeholders
end-users
marketing
&
sales
business
managers
out sourcing
vendor
vendor liaison
Webengineers
Cont ent
developers
We b
publisher
support
specialist s
administ rat or
(a) outsourced development
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
12/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005 1
WebApp Outsourcing - I
Initiate the project by performing the following tasksinternally
Gather requirements
Develop a rough design
Develop a rough schedule with delivery dates Consider increments
Make a list of responsibilities
For in-house staff
For outsourcing vendor
Define liaison mechanisms
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
13/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005 1
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 return-
on-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
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
14/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005 1
WebApp Planning - In-House
Understand scope, the dimensions of change, andproject 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
-
7/30/2019 Chapter 17 - Formulacin y planeacin para ingeniera Web
15/15
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are providedwith permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005 1
WebE Worst Practices
We have a great idea, so lets begin building theWebAppnow.
Stuff will change constantly, so theres no point in trying
to understand WebApp requirements.
Developers whose dominant experience has been intraditional software development can develop WebApps
immediately. No new training is required.
Be bureaucratic.
Testing? Why bother?