Scribd
Upload
5 views

software engineering case study

The document outlines a practical exercise for crafting a comprehensive questionnaire aimed at gathering software requirements. It includes sections on general information, functional requirements, non-functional requirements, user and documentation needs, and additional considerations, with specific questions designed to elicit detailed responses from stakeholders. The goal is to ensure a thorough understanding of the software's purpose, features, and requirements.

Uploaded by

Raj Desai
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

software engineering case study

The document outlines a practical exercise for crafting a comprehensive questionnaire aimed at gathering software requirements. It includes sections on general information, functional requirements, non-functional requirements, user and documentation needs, and additional considerations, with specific questions designed to elicit detailed responses from stakeholders. The goal is to ensure a thorough understanding of the software's purpose, features, and requirements.

Uploaded by

Raj Desai
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

22DCS015 CSE301 Software Engineering

PRACTICAL 3
Aim: To craft a comprehensive questionnaire for gathering software
requirements, begin by clearly defining the software's purpose and
identifying all stakeholders involved. Structure the questionnaire with a
concise introduction and distinct sections addressing various facets of the
software. Utilize a blend of open-ended and closed-ended questions,
ensuring they are neutral and unbiased. Incorporate both functional and
non-functional requirements into the questionnaire.

Questionnaire:
1. General Information

1. What are the key goals and objectives of the project?

2. Who are the stakeholders in the project?

3. What is the deadline for the completion of the project?

4. What is the budget for the project?

5. Specify the target audience for the software.

2. Functional Requirements

1. What are the core functionalities to be implemented in the


software?

2. Identify the key/priority features of the project.

3. What type of software is required (e.g., website, mobile


application, desktop app)?

4. Does any similar software or product already exist? If so, what


features can be adopted or improved?
22DCS015 CSE301 Software Engineering

5. What is the workflow of the software (describe the typical flow of


actions a user might take)?

6. What are the sources of data, and how will it be collected and
processed?

7. How should user feedback be incorporated into the design and


development process?

8. What type of data will the software need to handle (e.g., text,
images, real-time data, etc.)?

3. Non-Functional Requirements

1. What are the security requirements of the software (e.g.,


encryption, authentication)?

2. What are the hardware and software compatibility requirements for


the product (e.g., operating systems, browsers)?

3. How should the software handle failures and errors (e.g., logging,
user notifications)?

4. What are the scalability requirements (e.g., how should the


software scale with increasing users)?

5. Should the software be flexible to accommodate future


requirements or changes?

6. What are the cultural and regional considerations that should be


taken into account (e.g., language support, legal compliance)?

4. User & Documentation Needs

1. Are there any specific documentation needs for the project (e.g.,
user manuals, technical documentation)?

2. Are there any training requirements for users or administrators?


22DCS015 CSE301 Software Engineering

3. What user support services will be provided (e.g., help desk,


FAQs, troubleshooting guides)?

5. Additional Considerations

1. How will the success of the project be measured (e.g., KPIs, user
satisfaction, system performance)?

2. Are there any other specific requirements or considerations not


covered in the previous sections?

You might also like