SoftwareRequirementCaseStudyTemplate资源-CSDN文库

需积分: 9 128 浏览量 2011-12-28 06:47:50 上传评论收藏 4.33MB PDF 举报

### 软件需求案例研究模板 #### 概述本文档提供了一个关于软件需求规格说明的案例研究模板，特别是如何进行公司员工访谈的过程。该案例研究基于Argole Systems Inc.（前身为Catalisse, Inc）的实际项目，这是一家美国公司，在巴基斯坦拉合尔设有开发办公室。该公司的目标客户主要是基于美国的医疗机构。Argole Systems正在为美国市场构建最大的、独特的肿瘤科医疗产品，并且开发了多种Windows、Web和iPhone平台上的医疗应用。 #### 软件需求工程过程 **需求工程**包括所有生命周期活动，旨在对用户需求进行分类、分析以推导出补充需求、记录这些需求与用户需求的关系以及支持这些活动的过程。在这个案例研究中，我们探讨了需求工程实践在工业层面的应用情况。 #### 关键概念 - **V&V（验证与确认）**：确保软件满足其预定用途的过程。 - **QA（质量保证）**：一套管理方法，确保软件开发过程中遵循了适当的质量标准。 - **SQA（软件质量保证）**：软件质量保证是软件工程的一个子领域，关注于软件产品的质量保证。 - **SCM（软件配置管理）**：一种用于管理软件版本控制的方法。 - **SCI（软件配置标识）**：识别软件配置项的过程，以确保软件的不同版本可以被追踪。 - **CR（变更请求）**：正式提出的对现有软件或系统的更改建议。 - **PM（项目经理）**：负责项目规划、执行和完成的个人。 - **SVN（Subversion）**：一种流行的开源版本控制系统。 - **FS（功能规格书）**：定义系统或软件所需功能的技术文档。 - **RDD（需求设计文档）**：包含需求分析结果及其设计决策的文档。 - **SCCB（软件变更控制委员会）**：一个由代表不同利益方的成员组成的小组，负责评估、批准或拒绝变更请求。 - **CC（CruiseControl）**：一个持续集成工具，自动构建和测试软件项目。 - **RE（需求工程）**：涉及软件需求获取、分析、文档化和管理的一组活动。 - **QIP（质量改进范式）**：一种旨在提高产品质量和过程效率的方法论。 #### 需求工程实践分析在本案例研究中，我们对Argole Systems Inc.的需求工程实践进行了分析，特别关注以下几个方面： 1. **识别利益相关者**：了解所有可能影响或受项目影响的人或组织。 2. **需求收集**：通过访谈、问卷调查等方式从利益相关者那里收集需求。 3. **需求分析**：分析收集到的需求以确定项目的可行性并定义需求的优先级。 4. **需求文档**：创建详细的需求文档，如功能规格书和需求设计文档。 5. **需求验证**：确保需求正确无误，符合用户的期望。 6. **需求管理**：跟踪需求的变化，并确保所有变更都经过适当的审查和批准。 #### 实践中的关键步骤 - **需求收集**：通过对公司员工的深入访谈，了解他们对于新系统或功能的具体需求。这通常涉及到多个部门，例如销售、客户服务和技术支持团队。 - **需求分析**：分析收集到的信息，将其转化为明确、可衡量的需求。这一步骤还包括评估需求的可行性和优先级。 - **需求文档化**：将需求编写成文档形式，通常包括功能规格书和需求设计文档。这些文档应清晰地列出每个需求，并提供足够的细节以支持后续的设计和开发工作。 - **需求验证**：通过原型或模型来验证需求的有效性。这通常涉及向利益相关者展示原型并收集反馈。 - **需求管理**：在整个项目周期内跟踪需求的变化，确保所有变更都经过适当的审批流程。这可能包括建立一个软件变更控制委员会(SCCB)，以管理和审核变更请求。 #### 改进与建议根据案例研究的结果，我们可以提出以下改进措施和建议： 1. **增加透明度**：通过实施更好的沟通机制来提高整个开发团队之间的透明度，确保所有团队成员都清楚项目的目标和进度。 2. **采用敏捷方法**：考虑采用敏捷开发方法，以更快地响应变化，并允许更频繁地交付软件更新。 3. **强化需求验证**：加强对需求的验证过程，确保所有的需求都是可行的并且能够满足最终用户的需求。 4. **培训与发展**：为员工提供定期的培训和发展机会，特别是在最新的软件开发技术和最佳实践方面。 5. **优化变更管理**：改善变更管理流程，确保所有变更请求都得到及时处理，并且变更对项目的影响最小化。 #### 结论本案例研究通过分析Argole Systems Inc.的需求工程实践，为软件需求规格说明提供了一个实用的模板。通过深入理解需求工程的过程，包括需求收集、分析、文档化和管理等方面，可以帮助公司在软件开发过程中更加高效地满足客户需求。此外，本研究还提出了一些改进措施和建议，以进一步提高软件项目的成功率。

资源推荐

资源详情

资源评论

PRACTICAL REQUIREMENTS ENGINEERING

INDUSTRIAL CASE STUDY OF ARGOLE SYSTEMS INC

SAJJAD ASIF, ZAHID AZEEM ALVI, NAVEED AHMAD, AAMIR RIAZ

{SAAO10, ZAAZ10, NAAE10, AARI10}@STUDENT.BTH.SE

BLEKINGE TEKNISKA HÖGSKOLA, SWEDEN

ABSTRACT - This document shows the case study

about the requirement engineering in Argole Systems

Inc (formerly Catalisse, Inc) which is an American

company. This document explains about the

requirements engineering process of this company

and it also has improvements and suggestions about

the process. This case study also shows analysis of

actual industry practices and theoretical concepts.

KEYWORDS

V&V (verification and validation), QA (quality

assurance), SQA (software quality assurance), SCM

(Software Configuration Management), Practice

(Hospital), Facility (Laboratory), SCI(Software

Configuration Identification), CR (Change Request),

PM (Project Manager), SVN (Subversion), FS

(Functional Specification), RDD (Requirements

Design Document), SCCB (Software Change Control

Board), CC (Cruise Control), RE (Requirements

Engineering), QIP (Quality Improvement Paradigm)

1. INTRODUCTION

Requirements engineering includes all life cycle

actions devoted to classification of user requirements,

analysis of the requirements to derive supplementary

requirements, documentation of the requirements

against user needs, as well as processes that support

these activities.[1] In requirements engineering

process, purpose of software systems is discovered

by identifying all stakeholders and their wants.

In this case study we diagnose that how requirements

engineering practices applies in the industrial level.

In order to complete this study we considered Argole

Systems Inc. It‟s an American company and has one

development office in Lahore Pakistan. The target

clients of this company is the USA based practices

and facilities. Argole Systems is building biggest and

unique Oncology Healthcare products for USA

market. Company is making different windows, web

and iphone based healthcare applications and we

assumed that company is following all required

practices in their development processes. We chose

this company because it‟s working on different

technologies and have different types of applications

for healthcare market and customers (physicians).

The products are market and customer oriented and

company is following Market Driven Requirement

Engineering and Bespoke processes. This report

explains all engineering processes which are being

used in this company to build their products which

are customer and market oriented. We also highlight

the challenges that we faced during the investigating

of the RE processes and other real life industry

issues.

1. 1 COMPANY PORTFOLIO

Argole Systems is a Physician led healthcare

software and services company. Argole Systems

provides software healthcare solutions that include

both the clinical and the business workflows of

subspecialty practices.

Akessa

is Argole Systems exceptionally complete

software for Oncology management. It deals with the

complication of Clinical and Business processes that

are unique to oncology. Akessa

application is build

for desktop but it‟s also available for web and iphone.

Argole Systems provides billing services for the

practices and facilities, company representatives

interact with the insurance companies and patients in

USA. Company head office is in Maryland, USA and

one development and services office is in Lahore,

Pakistan.

Argole Systems has particular hierarchy for

executives and management. It starts from Chief

Executive and then two vice presidents for

technology and services. There are development and

quality assurance managers who manage software

engineers and software quality assurance engineers.

One teams of billers also working in billing services

department. Management representative handles all

other managerial operations like finance, human

resource management. Argole Systems develop

products specifically for the healthcare and there are

certain customers. Customer‟s provide feedback and

organization add more features in the product to

make it more generalize. Following is organizational

structure of Argole Systems:

CEO

Vice President (Technology)

Vice President (Services)

Management

Representative

Manager

Development

Manager

Quality Assurance

Manager

Billing Services

QA Team Leads

Dev Team Leads

Relevant Staff

Departments

Billing Team Leads

Figure 1 – Organizational Chart

1. 2 COMPANY REPRESENTATIVE PERSON

We contacted with Mr. Imran Afzal who is Manager

Quality Assurance. He is experienced person and

involved in the requirement engineering processes.

He has more than 6 years experience in 3

organization. He is leading team of quality assurance

department. We conducted interview with this person

and completed our survey about this company. We

also contacted with Mr. Nouman Shehzad who is

involved in the requirements engineering process. We

asked him to fill one questionnaire.

1. 3 STRATEGY FOR EXTRACTING

INFORMATION

Our first goal was to choose an organization that has

experience in requirement engineering process. Other

goal was to choose an organization which has good

repute in the market, stable and mature. We try to

choose that company which can share their

information to us about their requirement engineering

process. We also tried to contact with a few other

companies but didn‟t receive good response from

them. We have few references in Argole Systems

because one of our member was the part of Argole

Systems. We had 2 hours video conference with Mr.

Imran Afzal. We already prepared our interview

questions that we discussed with him. We followed

the instructions that were provided in our course

literature to conduct a meeting with company

representative. We tried to cover all required areas to

conduct a comprehensive study. We also had better

idea about domain and process because one of our

team member (Mr. Sajjad) was also the part of the

company.

We conduct interview and this strategy was more

helpful to extract our desired information. We

followed our plan to extract information from the

relevant person. We had all types of questions about

the company, requirement engineering processes,

quality assurance, process improvements, software

configuration management and all other required

research areas. We asked both open-ended and closed

ended questions from the relevant person. In open-

ended questions we go in detail and came to know

about many information and research areas that were

new for us. Additionally, we asked to fill a

questionnaire from a member (Mr. Nouman Shehzad)

of requirement engineering process team. This

approach also helped us to get information in detail.

This was our overall strategy to extract information

and knowledge of an organization.

1. 4 AIMS & OBJECTIVES

This report will discuss about the requirement

engineering methods implemented in an organization

and then relate those methods in provided literature

resources. We will identify real challenges that are

being faced in the industry related to requirement

engineering process. The main idea behind this case

study is to observe the requirement analysis process

of the organization. This report will also shows

requirement engineering gap analysis between actual

company and theoretical studies. It will help to figure

out strengths and weaknesses of the organization in

requirement engineering processes.

2. RESEARCH METHDOLOGY

First we designed our interview questions and

questionnaire with the help of previous year‟s case

studies and our course contents literature. We

conducted interview. During interview we divide our

questions in 3 sections. First section was about

personal and company introduction, second was

about requirement engineering processes and third

was about configuration management, quality

assurance and process improvement. We requested to

fill one questionnaire from a requirement engineering

process team member. We also did analysis of his

response about the provided questions in

questionnaire. We used qualitative research approach

to get in depth understanding. Qualitative method

helped us to get appropriate knowledge and

information about requirement engineering process of

Argole Systems by inspecting i.e. „why‟ and „how‟.

3. REQUIREMENT ENGINEERING

PROCESSES

Most of the clients of Argole Systems Inc. are

practices and facilities who want software according

to their need and Government‟s standard. Argole

Systems is fundamentally focused on developing

practices and facilities applications and is working

with both bespoke and market driven clients.

Generally clients interact with RE team of Argole

System and explain their requirements all the way

through their own marketing department and IT

department and other interested stakeholders.

In Argole System, RE is project centered and

requirements elicitation starts in project initiating

process and Scrum technique is used. The

requirement engineering starts with requirements

elicitation at head office in USA by the RE team.

Same kinds of actions are performed before and

during the project.

3.1 REQUIREMENT ELICITATION

Following activities are executed in requirements

elicitation process at Argole System.

3.1.1 GLANCE AT REQUIREMENT

ELICITATION

Requirements elicitation is the process of gathering

the requirements for system users, clients and

stakeholders [7]. Requirement elicitation is practice

of extracting, recognizing or finding out needs of all

kinds of stakeholders [8]. Requirements elicitation is

known as individual of the most important

knowledge-intensive actions of software

development [9]. Poor implementation of elicitation

will nearly assure that the absolute project is a total

failure. Since project malfunctions are so

uncontrolled [10], it is pretty possible that improving

how the company performs elicitation might have a

spectacular effect on the success proof of the

company [11]. Improving requirements elicitation

has need of us to first be aware of it. While many

documents have been published that describe

elicitation, or set down a specific method to execute

during elicitation, no one has yet described a

cohesive model for elicitation process that highlight

the role of information.

3.1.2 COMPANY’S PROCESS OF ELICITATION

In requirement elicitation process, first step is

identifying the stakeholders in the client practices and

facilities. Elicitation start when clients are identified.

In most of the projects, elicitation process consists of

conducting interviews (individual and group),

observation of employees work activities and collect

information from practices and facilities manuals etc.

In Argole System, elicitation process is continuously

performed during whole software development life

cycle. The elicitation process is performed by the RE

team of head office in USA. RE team of head office

in USA conduct elicitation meetings with the clients

and collect requirements from stakeholders in form of

user stories. These user‟s stories in raw formats are

sent to Lahore office. Then development and quality

assurance teams refine these. The requirements are

processed until the requirements become clearly

reasonable, assessable, computable etc.

In refinement process, user stories are partitioned into

single distinct comprehensible requirements. If the

requirements are still ambiguous or requirements are

not understandable then requirements are consulted

with the RE team in USA. RE team set more

elicitation for these ambiguous and complicated

requirements until these requirements are clear and

understandable. The RE process of company is

described in Figure 2.

3.2 REQUIREMENT SPECIFICATIONS

Documenting the functional requirements, non

functional requirements and external interfaces in a

way called requirement specification. IEEE 830-

1998 Standard template is being used to write these

kinds of requirements.

Figure 2 – Requirement Engineering Process

3.2.1 GLANCE AT REQUIREMENT

SPECIFICATION

The documented requirements should not consider as

final. Then RE Department further improve and sort

out the requirements in order to declare these

requirements are valuable and fulfill the

functionalities or not. After sort out these

requirements are sent back to the customer for

verification. Customer satisfaction is very important

for software industry. Stakeholders may produce

documentation as required. A single Iteration may

not add enough functionality to demand a market

release, but the goal is to have an obtainable release

(with minimal rate of bugs) at the end of each

iteration [3]. Various iterations may be requisite to

release an artifact or new features.

3.2.2 COMPANY’S PROCESS OF

SPECIFICATIONS

Quality assurance team of Argole systems is

responsible for documentation of requirements.

Argole systems follows the agile development

method. Agile processes tie together change for the

customer's competitive advantage”, “Deliver function

properly part of software frequently, from a couple of

days to a couple of weeks, with a preference to the

limit timescale” [4]. According to the Interview,

Argole system doesn‟t use a Formal Software

Requirement Specification the (IEEE Std 830-1993),

and as a substitute they are using “Product Backlogs”

which is “perhaps the single most important artifact

in an agile project” [5]. According to an experimental

Study [6] the product backlog has focused on the

functional requirement.

Product Backlog is created by the Customer (in agile

it called “Product Owner”), then it send to developers

(in agile they are called “Scrum Team”), and they

estimate about each user story cost. By using “Story

Point” they estimate the scale value between (1- 4),

where 1 is the lowest value and 4 is the highest value.

After then estimated backlog shown to the Product

Owner and prioritize the list, what they would like to

see in the first sprint to make what is called “Sprint

Backlog”. This all process us being used in Argole

Systems.

3.3 REQUIREMENT’S VERIFICATION AND

VALIDATION

Following activities are executed in Verification and

Validation process at Argole System Inc.

3.3.1 GLANCE AT REQUIREMENT’S

VERIFICATION AND VALIDATION

For sustaining the quality of everything, verification

and validation all the time plays significant role.

Requirement verification and validation are different

terms, as verification makes sure that the product

matches the requirements which are important for

system functionality. Validation illustrates to confirm

that it is fulfilling the client‟s requirements or not

[12]. Requirement specification would be the input of

Verification and Validation and a developed form of

requirements are as an output.

3.3.2 COMPANY’S PROCESS OF

REQUIREMENT’S VERIFICATION AND

VALIDATION

Matured processes are used for requirement‟s

verification and validation in Argole System. Three

departments deal in the verification and validation

process. i.e. USA office, Quality Assurance and

development departments from Lahore office.

Requirements are verified with different techniques

which are a combination of different testing

techniques checklists and use case scenarios and

requirements are also validated by these departments.

Both departments of Lahore office are not only

verifying and validating for the requirements, but

also liable for the verification and validation of all

phases during the project such as development,

architecture and design. It is the strong point in

verification and validation process that same

departments are verifying and validating

requirements which are also performing quality

assurance of all aspects of product. Quality

Assurance department defines the verifications

process and also validation for other phases of

projects. Internal and external reviews are done.

Inspection is being performed within the

departments. Most of time, teams do walkthroughs

and audits to verify and vaidate the requirements.

3.4. REQUIREMENTS ANALYSIS AND

PRIORITIZATION

Requirements prioritization is very important for all

stakeholders. In this section we shall focus on

techniques for requirement analysis and prioritization

used in Argole System.

3.4.1. GLANCE AT ANALYSIS AND

PRIORITIZATION

Prioritization is a process in which we order the

requirements according to the importance and

minimized the number of requirements. Requirement

analysis is the understanding the Software

Requirement Specification more in depth and it is the

qualification for the requirements prioritization.

Requirement prioritization removes the divergence

among stakeholders of the system. Requirements are

prioritized with respect to cost, and value (time and

effort). There are many prioritization methods (e.g.

100 $ method, Interaction Matrix, Planning Game,

Top 10 Requirements, Quality Function deployment,

analytical hierarchy method, Boundary definition,

Ranking, negotiation with the customer, MuSCoW,

Grouping, and others etc.) methods for prioritization

[13].

3.4.2. COMPANY’S PROCESS OF ANALYSIS

AND PRIORITIZATION

In Argole Systems, firstly requirements are analyzed

and then prioritized. In customer oriented products,

requirements prioritization is precisely followed

according to the client‟s will or by negotiation with

the client. Requirement prioritization for the market

driven products are done with respect to the cost-

value. Argole Systems does not spend much on the

requirement analysis and prioritization if time limits

and customer state of affairs are ideal than they just

rely on “allow the development team what to do”.

During release days, requirements are prioritized with

respect to the client‟s wishes.

3.5. REQUIREMENT MANAGEMENT

Requirement management deals with the requirement

change management, Traceability, Requirement

Reuse, and process improvement.

3.5.1 GLANCE AT CHANGE MANAGEMENT

Requirement management also describes the theory

of requirements change management. Requirements

are very important to organize. If requirements are

not managed properly then it may cause the failure of

project. Requirement change management provides

us the systematically to keep all the changes in track

within the requirements [14].

剩余162页未读，继续阅读

评论收藏

内容反馈

yini_chai

粉丝: 0
资源: 2

Software Requirement Case Study Template

最新资源

Software Requirement Case Study Template

Software Requirement

Software Requirements Specification

Practical Software Requirements

软件需求Software Requirements(PDF)经典哦

软件需求规范模板Software Requirements Specification Template

SoftwareRequirements

[E-book]MsP,.Software.Requirement.Patterns.(2007)

Case Study Research in Software Engineering

The Influence of Organizational Structure On Software Quality - An Empirical Case Study (tr-2008-11)-计算机科学

实用软件工程 Practical Software Engineering:A Case Study Approach

use case driven approach for software engineering

软件需求分析-用例分析

Mobile Software Test Case.rar

experimental study in software enginnering

!Model-Driven Software Development with case study.pdf

case study

软件需求 software requirements

experimental study in software engineering

Software Project Plan Template

SRS -software requirement specification-user story

software testing use case

software requirements 软件需求

requirement sample

A Case Study in Successful Risk-Based Testing at CA

最新资源