Course: Software Modeling and Analysis, Section: TOPIC 2- TYPES OF REQUIREMENTS

General

Course Leader Details Forum

Ms. Noor Zuhaili bt Md Yasin

Master in Computer Science (Software Engineering), Universiti Putra Malaysia

Field of study: Software Engineering, Programming, Knowledge Management (Ontology)

: zuhaili@nilai.edu.my

S222, Science Block (School of Computing, FEST)

: 012 3634344

Thursday (10-12pm), Friday (8-10am)



Topic 1	Requirement Analysis and Specification
	1.1	Understanding the business, the organization and its system
	1.2	Specifying Requirements
	1.3	List and describe the contents of the Requirements Specification
	Summary


Topic 2	Types of Requirement
	2.1	Distinguish between the different types of user requirements including functional, non-functional and constraints (or pseudo requirements)
	2.2	List and describe the techniques used by the analyst to elicit requirements from different users
	2.3	Interview
	2.4	Questionnaire
	2.5	Observation
	2.6	Document Reading
	2.7	Requirement Specification and Validation
	2.8	Explain how modelling the required system in the analysis of requirement
	Summary


Topic 3	Requirement Model
	3.1	Explain the value of use case diagram, as a tool for doing Functional Requirement Analysis
	3.2	Draw use case diagram
	3.3	Write use case description
	3.4	Data dictionary
	Summary

Topic 4	Object Oriented Technology
	4.1	Describe some of the fundamental concepts of Object Orientation
	4.2	Explain the difficulties inherent in moving from the use case diagram to written code and how sequence diagram may aid this process
	Summary


Topic 5	Scenario Analysis
	5.1	Describe business process and the interaction of an information system with its environment
	5.2	Draw activity diagram


Topic 6	Construction of OO Structural Model
	6.1	Identification of objects and classes
	6.2	Draw class diagram
	6.3	Interaction diagram and state diagram
	Summary

Kindly refer to the attached links to download "points to note " and cover page.

1. https://drive.google.com/file/d/1VCkzl6n1_u79t3Dvw94ut-F0HMoheBJS/view?usp=share_link

2. https://drive.google.com/file/d/11QHdYjYXW9kui3agRj8ls-DGMp_O6I4-/view?usp=share_link

INTRODUCTION TO THE COURSE

Hi! Welcome to OEC3114 (Software Modelling and Analysis) Class.

This course introduces the principles, methods and techniques for the development of automated information systems. The course will cover the analysis stage and will use Object Oriented techniques to develop an application.

CONTINUOUS ASSESSMENT SCHEDULE

This course is assessed by both coursework and examination.

NZMY~

TOPIC 2- TYPES OF REQUIREMENTS

LEARNING OUTCOMES

By the end of this topics, you will be able to:

1. Describe the FR and NFR

2. Discuss the techniques might be use to elicit requirement

3. Explain on how to modelling in the requirement analysis

INTRODUCTION

The analysis phase is so named because the term analysis refers to breaking a whole into its parts with the intent of understanding the parts’ nature, function, and interrelationships. In the context of the SDLC, the outputs of the planning phase (the system request, feasibility study, and project plan), outline the business goals for the new system, deﬁne the project’s scope, assess project feasibility, and provide the initial work plan. These planning phase deliverables are the key inputs into the analysis phase. In the analysis phase, the systems analyst works extensively with the business users of the new system to understand their needs from the new system.

SUMMARY

Functional Requirement And Non- Functional Requirement

A requirement is simply a statement of what the system must do or what characteristics it needs to have. During a systems development project, requirements will be created that describe what the business needs (business requirements); what the users need to do (user requirements); what the software should do (functional requirements); characteristics the system should have (nonfunctional requirements); and how the system should be built (system requirements). Although this list of requirement categories may seem intimidating at ﬁrst, the categories merely reﬂect the purpose of the requirements and the stage in the SDLC in which they are deﬁned.

Elicitation Techniques

Topic 2- Video Lecture (Duration: 1 hour) File

According to this video, student be able to explain functional requirements - the specifications of the product’s functions (features). Simply put, functional requirements define what precisely a software must do and how the system must respond to inputs. Functional requirements define the software's goals, meaning that the software will not work if these requirements are not met'.
Self-Check 2.1: Quiz (Duration: 0.5 hour)

Restricted Not available unless: The activity Topic 2- Video Lecture (Duration: 1 hour) is marked complete
Self-Check 2.2 (Duration: 0.5 hour) Quiz

SELF CHECK 2.2

4. Distinguish between business, user, and functional requirements.

5. Explain what is meant by a functional requirement. What are two types of functional

     requirements? Give two examples of each.

6. Explain what is meant by a nonfunctional requirement. What are the primary types of

    Nonfunctional requirements? Give two examples of each. What role do nonfunctional

    requirements play in the project overall?

7. What is the value of producing a requirements definition and having the project sponsor and key

     users review and approve it?
Self-Check 2.3 and 2.4 (Duration: 1 hour) Quiz

SELF CHECK 2.3

8. What are the three basic steps of the analysis process? Is each step performed in every project?

      Why or why not?

9. Discuss the appropriate way to set up and conduct interviews to elicit requirements.

10. Give an example of a closed-ended question, an open-ended question, and a probing question.

       When would each type of question be used?

11. “Interviews should always be conducted as structured interviews.” Do you agree with this

        statement? Why or why not?

SELF CHECK 2.4

. 12. Why is document analysis useful? What insights into the organization can it provide?

13. Outline suggestions to make observation a useful, reliable requirements elicitation technique.

14. Describe a strategy for using the various requirements elicitation techniques in a project.

15. Discuss problem analysis as an analysis strategy. What are the strengths and limitations of this

        technique?
SIM Lecture Note- Topic 2 (Duration 1 hour) File

General

TOPIC 2- TYPES OF REQUIREMENTS

TOPIC 2- TYPES OF REQUIREMENTS

Contact Us