[go: up one dir, main page]
Scribd
Upload
8 views20 pages

Chapter 3 - Methodology

Chapter 3 outlines the methodology for a project, detailing the target group, sampling methods, and data collection techniques such as questionnaires and interviews. It specifies functional and non-functional requirements for the system, including user access and performance metrics, and describes the testing plan and coding languages to be used. Additionally, it includes references and appendices for work plans, budgets, and interview guides.

Uploaded by

benardlusisa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views20 pages

Chapter 3 - Methodology

Chapter 3 outlines the methodology for a project, detailing the target group, sampling methods, and data collection techniques such as questionnaires and interviews. It specifies functional and non-functional requirements for the system, including user access and performance metrics, and describes the testing plan and coding languages to be used. Additionally, it includes references and appendices for work plans, budgets, and interview guides.

Uploaded by

benardlusisa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Methodology

Chapter 3
Introduction
• Introduction of the chapter
• What will the chapter have
Where will it be used
Locality of the
Project/Beneficiary Who are you designing for?

Think beyond the name user


Sample (Target Group)

Define target group Define who you plan to target for


the data collection
Sampling Method

• What sort of sampling method will you use?


• Random Sampling
• Cluster Sampling
• Snowball Sampling
Data Collection Method

• How will you collect your data


• Questionnaires
• Interviews
• Observation
• Field Research
Based on the data collection

What data will you Qualitative


collect Quantitative

Data Analysis
How will analysis be Thematic
done Descriptive statistics

Consider the HCI class


What model will you use
• Rapid Prototyping
• Waterfall
System • JAD
Analysis • Agile

What are the phases

Why did you choose that type


System Design
Functional Requirements
When the user enters the information, the system shall send an approval request.

The server shall log all changes to existing data.

When 24 hours have passed since the last database backup, the server shall automatically back up
the database.
The local terminal shall automatically print a list of orders every 4 hours.

When the local time is 0800, the server shall email a report of open issues to all managers.

The system shall only allow managers to view customer banking data.
Non-functional requirements

• Emails should be sent with a latency of no greater than 12 hours.


• Each request should be processed within 10 seconds.
• The site should load in 3 seconds when the number of simultaneous users are > 10000
• If a user has not changed their password for 56 days, then the system shall require a
password change upon login.
• The system must accommodate a minimum of 3 million concurrent users.
• All web pages shall load within 4 seconds.
• The server room shall accommodate a future doubling of installed hardware.
• The server room shall be accessible by authorized employees 24 hours per day.
Use Case
Diagrams
Context
Diagram
How will you test the system?

What levels will you have


Testing Plan • Unit Testing
• Integration Testing
• System Testing

Consider Software Engineering


class
Coding language to use

System Database to implement project


on
Development

Other languages to be
incorporated
References
• Should be in APA
• All references should be captured
Appendix

Final
Appendix 1 Work Plan/ Gantt Chart
Appendix 2

BUDGET COSTS ASSOCIATED WITH THE


PROJECT
Appendix 3

QUESTIONNAIRE INTERVIEW GUIDE

You might also like