Three- Reflective Journal

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 1/4

MODULE 5MODULE 5

Requirements reuse, requirements for speci�c project

classes

Source: https://towardsdatascience.com/my-best-tips-for-agile-data-science-

research-b40365cc979d?gi=3bce73833258

Introduction:

The �rst module of this Subject taught you an overview of requirements

engineering, then discussed the various types and levels of requirements,

and the characteristics of a good requirement statement. The following

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 2/4

three modules focused primarily on requirement elicitation, requirement

analysis, requirement speci�cation and requirement validation. Before you

learn the �nal key process in requirements engineering, viz. requirement

management, you will learn some miscellaneous topics in requirements

engineering, namely, requirement reuse and requirements for speci�c

project classes.

Reusability lies at the heart of software engineering. Increased reusability

translates to e�ciency and faster delivery time, which will result in reduced

defects, cost and risk. Software engineering practices seeks way to reuse

components of software that has been previously developed. However,

most reuses are concerned about reuse of code through, for example, the

design of loosely coupled software modules. Even a beginner in

programming would be taught to use “functions” or “method” so that the

functions can be reused at a micro-level. However, can requirements also

be reused?

Requirements can also be reused, and there are many reuse opportunities.

For example, business processes are similar across di�erent organisation.

Student enrolment process at Torrens University, albeit not identical, is not

too much di�erent from that at a di�erent university. From a user interface

perspective, the login forms all look similar from one another on various

website. From a non-functional requirement perspective, there may be

industry standards cross all organisations on, for example, the security level

of their apps. All of these provides rich opportunities for requirement reuse.

In the �rst half of this Module, you will learn the three dimensions of

requirements reuse, they are the extent of reuse, extent of modi�cation,

and reuse mechanism. You will also learn the requirements reuse barriers

and success factors.

In the second half of this Module, you will learn requirement engineering

practices for speci�c project classes. In particular, you will focus on Agile

Projects. You will �rst learn the limitations of waterfall approach (sequential

model) and agile development method. You should note that agile is not

referring to a speci�c development method; rather, it is a broad term that

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 3/4

encompass all development methods that subscribe to the agile manifesto

or the agile principles. Traditional waterfall method and agile method

handle requirements quite di�erently in a number of aspects. For example,

in terms the level of customer involvement, the level of document detail,

timing of requirement engineering activities, and the attitude towards

requirements changes.

You will learn how to tailor requirement practices to �t agile projects. For

example, the use of user stories, prioritisation on agile projects,

evolutionary prototyping.

This Module will cover:

Module 5.1 – Requirements reuse

Module 5.2 – Requirements for speci�c project classes

This Module will help you achieve the following outcomes:

a) Critically evaluate requirements management as it applies to a variety of business environments

b) Synthesise key principles to stakeholders to solve problems for requirements management, explore and demonstrate how these principles support systems engineering and life cycles

c) Identify, select and develop requirements to maximise e�ectiveness in the enterprise and promote sustainable business practices.

Time Management:

Your workload expectation is 20 hours for this module.

20 hours per module (two weeks): facilitated study: 3 hours / week. Personal Study: 7 hours / week. 

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 4/4

3 hours facilitated study consists of attending class, responding to facilitator feedback.

You are to allocate 7 hours of personal learning. This includes essential time spent on pre-reading and viewing materials, assessment progression and learning activities.

Assessment Progression:

Assessment 3 is due at the end of module 6.1 (week 11). Please refer to the

assessment briefs in the assessment area for more detail.

Make sure you download and read the Assessment Brief as soon as it is

available and ask the learning facilitator if you have any questions.

Student Expectation:

You are expected to have worked through the essential learning resources and activities for this module before attending the facilitated session (face to face or online session) – this enables informed discussion and full participation in learning activities.

Participate in all scheduled facilitated sessions.

This time is intended to be used by you and your learning facilitator to work through activities and engage in discussion about the module content.

These sessions provide a space for you to raise questions about the module content and seek guidance on writing your assessments.

You will review, explore and discuss more deeply the information presented in the learning resources.