Systems Test 2

Assume an 8 hour day, 14 person hours with team of 3. how many total person days is required? how many actual days?

14*45=630 630/8=79 79/3=26.33 days

Brief use case

A brief summary use case that provides only a highest level summary description of the user's goal.

Anchoring

A cognitive bias in which a team member's estimate of a software item is unduly influenced by an estimate already announced by (an)other team member(s). The earlier estimate is the "anchor."

Annuity

A fixed amount of money paid or benefit received for a series of time periods (typically, yearly).

Mock-up

A highly abstract model of an application or a web page that defines key structural elements without details.

Wireframe

A highly abstract model of an application or a web page that defines key structural elements without details.

Design thinking

A process model for designing product and service innovations.

Feasibility analysis

A process to determine whether or not it is reasonable to expect that a project can be completed successfully.

COCOMO II

A quantitative model that can be used to estimate software effort, costs, and duration based on unadjusted function points (or lines of code) and a series of adjustment factors pertaining to the overall project environment, including elements of people, process, and product.

Function point analysis

A software cost-estimation approach that offers a standardized method of counting the design elements of a software application and evaluating their complexity.

Summary level use case

A use case narrative that describes a higher-level goal, such as a business process.

Sub-function level use case

A use case narrative that describes a system capability shared by multiple user goal level use cases.

Prototyping

A widely used methodology in product design in which models with limited capabilities are used as a mechanism for communication between designers and clients.

Perpetuity

An annuity in which the payments are made (or assumed to be made) forever.

T-shirt sizing

An approach to software cost estimation in which very-high-level requirements are used to generate rough estimates using category labels similar to t-shirt sizes: extra small, small, medium, large, extra-large, etc.

CRUD operations

Basic operations related to each entity instance in a database table: create, read, update, and delete.

Features using user stories:

Brief, one-line statements expressing capabilities that a type of user (or "actor," "persona," or a "role") should be able to access while interacting with the system to achieve some business goal or benefit. The standard formulation for expressing a user story is "As a <type of user/actor>, I want/need to <achieve some goal using application software> in order to <achieve a business goal or obtain business value>." This one-line description is sometimes supplemented with user acceptance criteria, which provide the basis for creating system test cases.

8.2.12 Team Characteristics

Customer team, Colocation with and availability to the IT team, Number of business stakeholder roles and level of variability in business practices, IT team, ◦ IT team size, IT team locations, ◦ IT team skill sets, IT team capability

New Capabilities =

New Capabilities = (Future State Capabilities - Current State Capabilities) + Refactoring

Accuracy vs. Precision

Precision The exactness of an estimate. For example, a cost estimate of $20,782.16 is highly precise but not necessarily accurate. Accuracy How close an estimate is to an actual value. For example, a cost estimate of $21,000 is highly accurate if the actual cost turns out to be $21,621.87.

Definition of done

Project planning section defining which process tasks—for example, in the categories of analysis, design, coding, testing, and deployment—must be done for each feature in order for the project to be considered to be complete.

Reducing uncertainty:

Regarding what capabilities are needed and how they should work

Delivery leaders

Run the project on a daily basis. Typically, this includes the product owner for the business and the project leader for IT.

Intelligent project planning

Selectively using up-front, formal project planning tools and techniques only when they add value for a specific project. This is based on project size, complexity, and other factors.

Internal rate of return (IRR)

The actual rate of return of a project. IRR is an alternative to NPV.

Weighted average cost of capital (WACC)

The discount rate (expressed as a percent) that represents a firm's overall cost of raising money. The WACC is the discount rate to be used in NPV cost/benefit analysis.

Business benefit

The monetary benefit of creating and implementing a new or enhanced software application.

Planning fallacy

The systematic tendency in projects to underestimate software costs and overestimate business benefits.

Year 0

The time in which a project delivering new or enhanced software is executed, including requirements, construction, and deployment. "Year 0" may be longer or shorter than twelve months but ends with the "go live" date.

Features:

What capabilities the system should provide, typically defined as stories and associated acceptance criteria

The Bond Electronics Project

1. Assumption and or risk (identified that is already a existing problem) 2. risk (high) 3. issue (disagreement) 4. Issue (Not qualified staff)

Calculate Unadjusted functions

1. Find External Inputs (EI), External Output (EO), External Query (EQ), Internal Logical File (ILF), External Interface File (EIF) 2. Enter PW and Authorization code (EI) 3. Activate/deactivate (EI) and (E0) 4. System Configuration File (ILF) (internal to system, provides info) 5. zone inquiry (EQ) 6. activate panic button (EI) 7. sensors (EIF) (we don't know a lot about system) 8. Monitoring and response system (EIF) 9. panic button and response (EI)

Use case diagram

A UML diagram type that provides a summary view of a system's use cases, their relationships, and actors.

User story

A brief narrative description that includes a user role, a need that is important for the user role, and a justification for the need.

Business case

A highly summarized set of information presented to senior decision makers for them to approve the project. Consists of the project vision, cost/benefit analysis, and summaries of the timeline, team, risks, and reporting plan.

User interface prototype

A model of an application with a limited implementation of key functionality.

User interface model

A model of an information system user interface that allows a user to explore the system's capabilities in an easily understandable way.

Use case slice

A part of a use case that can be implemented in a single sprint.

Statement of work (SOW)

A preliminary project plan incorporating and building on the project vision to describe the project in terms of specific scope, process tasks, timeline and milestones, the team, and risks and issues.

Project charter

A project plan that also includes approvals to proceed from senior decision makers. It consists of an updated SOW plus the project's financial justification.

Cost/benefit analysis grid

A tabular approach used in ROI analysis to compare systems project costs to benefits. Each cost and benefit is classified as "one-time," "capital," or "annual." Based on those classifications, the costs and benefits are allocated in each year of the planning horizon.

Decomposition

A technique to improve software cost estimates by decomposing large chunks of work to smaller, more detailed chunks of work.

Use case narrative

A textual document that articulates an integrated requirements description that is more comprehensive than a user story.

Engineering task

A unit of work that can be implemented during a single sprint separated from other work based on technical—not functional—characteristics.

Story points

A unitless, relative measure of the size of a user story or PBI, and an alternative to ideal days. Larger and more complex items are assigned higher numbers of story points.

User goal level use case

A use case narrative that describes a system feature that allows a user (role) to achieve a specific goal.

Epic

A user story that summarizes a broad range of user needs.

Net present value (NVP) analysis

An approach to investment cost/benefit analysis in which the monetary values in the future are reduced ("discounted") to reflect the time value of money. (A dollar today is worth more than a dollar tomorrow.)

Return on investment (ROI) analysis

An approach to investment cost/benefit analysis that considers the value of an investment several years into the future without considering the adjustments for the time value of money.

Expert judgment

An approach to software cost estimation in which expert(s) in requirements and development generate estimates by comparing a current user story or product backlog item to similar items build previously.

Planning poker

An approach to software cost estimation in which user stories or PBIs are estimated by the development team utilizing a consensus-based approach of all involved team members.

Cost/benefit analysis

An estimate of the costs incurred to create, deliver, and implement a software application.

Software cost estimate

An estimate of the costs incurred to create, deliver, and implement a software application.

Estimate

An informed prediction of a future outcome.

Traditional organization

An organization that values highly predictable and low-risk creation of software capabilities.

Agile organization

An organization that values rapid delivery of software capabilities in a highly responsive manner with respect to changing software requirements.

Persona

An organizational role in which an individual uses an information system to achieve a goal.

Example of user story

As a <name of the user role>, I want to <the user's goal in the user role> so that <a justification for the goal> As a customer within a retail store, I want to be able to easily find a product that fits my needs so that I can pick up my purchases accurately, efficiently, and without delays.

Detailed User Stories

As a customer in a retail store, I want to be able to use my own portable device to easily find a product within the store that fits my needs so that I can complete picking up my purchases accurately and efficiently. As a customer in a retail store, I want to be able to use my own portable device to identify the physical location of a specific product based on its name or an image of its packaging so that I don't waste time searching for the products that I want to buy.

4.4.2 Creating UI Models Associated with User Stories

As a customer in a retail store, I want to be able to use my own portable device to identify the physical location of a specific product based on its name or an image of its packaging so that I don't waste time searching for the products that I want to buy.

Acceptance criteria

Criteria that have to be fulfilled for an implementation of a user story to be acceptable. These serve as constraints that limit acceptable implementation options.

Knowledge creation:

Determining the requirements among a subset of key team members focused on SA&D. This is typically accomplished via a BA and/or a product owner working with various business stakeholders, sometimes with the involvement of a scrum master or software development leader.

Greenfield development

Development of an entirely new system.

Brownfield development

Enhancement of an existing system.

Senior project sponsors

Executives who bear overall responsibility for project success. Although not involved on a daily basis, they oversee the delivery leaders, champion the project, and make major decisions.

Domain models using entity-relationship diagrams (ERDs) and class diagrams:

For modeling concepts within the domain, including entity types, specific attributes of the entity types, and associations between the entity types.

Business processes using activity diagrams:

For modeling high-level business processes. These diagrams illustrate the flow of activities used for the process, often tying the business process activities to specific actors using the swim-lane diagram format. Many see activity diagrams as a type of flowchart.

User experience/user interface (UX/UI) using wireframes, mock-ups, and prototypes:

For modeling how users will interact with the system.

Functional designs:

How the system will provide those feature capabilities in terms of software processes and logic, data, and user interfaces

Solution designers

Include business subject matter experts, IT BAs, architects, and others focused on the details of delivering the solution. They are especially important in large projects with complex scope.

Knowledge Sharing:

Once information about the requirements has been created, it must be efficiently shared with other team members—especially the software developers and testers. In other words, it does no good to design a solution to a business problem if, for example, software developers in another location cannot grasp the design details needed for them to program the solution.

Scope definition

Prioritized list of features to deliver. These priorities serve to define minimum and maximum scope.

Cost/benefit analysis

Process of systematically evaluating whether to approve a systems project, based on estimating both costs and benefits and comparing the two.

System capabilities

Specific features—what the system will do and how it supports users in their work—that are planned to be delivered to address a business problem or opportunity.

Ideal days

The amount of time a user story or product backlog item is estimated to complete under ideal conditions.

Fully dressed use case

The most comprehensive use case narrative format.

Go live

The point in time when new or enhanced software capabilities are implemented in production, such that the business can begin realizing anticipated business benefits.

Intelligent modeling

The principle of creating requirements artifacts only when they add value in a given project context at a particular stage of the process.

Monetization

The process of finding ways to take nonmonetary assets or capabilities and turn them into quantifiable economic value or, put more simply, finding ways to make money with them.

Business benefits

The value to an organization—typically able to be quantitatively estimated in monetary terms—of a series of planned systems capabilities.

Casual use case

Use case narrative offering a moderate level of details, more than a brief but less than a fully dressed use case.

User interface (UI)

User interface (UI) refers to the interfaces (typically web pages, mobile app screens, or other visual approaches; others, such as audio, also exist) with which a user interacts with the system, navigates between screens, and views information in the form of reports charts and other data visualizations.

Sensemaking:

Working with others through data collection, action, and conversation to create and test a plausible understanding—an overall, integrated model—of a solution to a business need in the form of an opportunity to exploit or a problem to solve. That model describes the path forward to build a system that meets the business need

What types of criteria could help further constrain the solution set for this user story? For example, consider the following:

• A location identification solution is available on the two most popular mobile computing platforms (currently Android and iOS). • The user will be able to identify the desired product by entering (a part of) its name or its universal product code (UPC). • If the desired product is not available in the store, the solution will indicate whether the store typically carries it and, if it does, when it is expected to be available again. • The solution will communicate the location to the customer as an aisle/bay combination or the solution will communicate the location to the customer on a map that shows directions from the customer's current location to the product location.

Dimensions of Feasibility:

• Economic • Financial • Technical • Schedule • Political • Operational • Legal, regulatory, and contractual • Environmental sustainability

Four Key Business Goals

• Increase margins: Invest in systems to maximize bottom-line profits earned on given amount of revenue. • Increase revenues: Invest in systems to boost top-line dollars on which profits may be earned. • Stay in business: Maintain systems to continue to generate existing revenues and margins. • Other improvements: Provide value to stakeholders that does not directly contribute to revenues and profits, but which are consistent with the organization's mission to serve its stakeholders.

INVEST Model

• Independent (of other user stories) • Negotiable (one that leaves space for negotiation during construction) • Valuable (for the client) • Estimable (one that provides a sufficient foundation for a good approximation) • Small (allow its completion within a specific construction cycle) • Testable (particularly when evaluated together with acceptance criteria)

12.3.6 Team Roles and Organization

• Product owner: A businessperson empowered to determine what scope should be delivered and the priorities for that scope. • Scrum master: The "servant leader" of the IT development team. This means providing the team with advice, guidance, and helping remove obstacles. It is not supposed to mean telling the development team how it should be organized or what each team member should do, as per the traditional role of a project manager. • Development team member: An IT team member focused on rapidly and frequently delivering working, "potentially shippable" software. Each team member should have a broad set of skills, enabling cross-functional work—development, UX/UI design, testing, and more. Further, as a group, the development team should be self-organizing. This is supposed to promote team member commitment and informally collaborating to accomplish the work in the most effective fashion.

8.2.8.1 The Minimum Contents of a "Fully Dressed" Use Case

• Story: That the use case is expanding into greater detail • Use case revision/approval information:◦ Story owner◦ Story creator◦ Revisions and approvals • Main scenario • Alternative scenarios/extensions • Acceptance criteria • References and attachments: Integrating the use case to other, related software requirements

10.4 Software Construction Project Cost Estimating Approaches

• T-shirt sizing • Planning poker • Expert judgment • Function point analysis • Adjusted function points/COCOMO II