LEARN MORE...

CS 349 Software Engineering Discussion

Content type

User Generated

Subject

Software Engineering

Course

CS 349

Type

Discussion

Uploaded By

Bzrtnanhg

Pages

Showing Page:

1/3

Kodie Turner

CS349

5/6/20

In software engineering, we need to be clear about the requirements about the project before we

dive deep into its formatting and development. The part where we do research and discover the

requirements of a system from user's perspective, customer’s perspective and from the eye of other

stakeholders. The segment where we allocate the practical requirements of system is a vital cog in

the development of project. If its overlooked, the project can turn haywire with the time and spending

plan and could lead the team into a fizzled project.

Keeping in mind that there is not one single technique that suits all the scenarios, let us discuss

three different elicitation methods:

1.Brainstorming -

To generate ideas around a specific domain, we need to have planned brainstorming sessions. It is

the method where a group of people with their own set of ideas and imagination sit together and

discuss their viewpoints without any inhibition or censoring the ideas, and this process has power to

look beyond obvious and leads to processes no one mentioned because it is an amalgamation of

numerous ideas. In this process, by expressing your own ideas, you come across several viewpoints

which are not completely in concurrence with you but due to healthy clash you come across newer

plans. Some of its salient features are that it’s a group method where all the ideas are documented

after or during the process so that every team member can view it.

Benefits: This method prevents one's gotchas as everyone travels down those roads which are new

for them and learn those things that they are unaware of. It enables one to gain plethora of

knowledge at once.

Showing Page:

2/3

Disadvantage: It can be too tedious job and can eat up a lot of time if not properly managed. Also,

certain unreasonable ideas can also crop up for discussions.

2. Interviews

In this technique you can directly talk to the stakeholders of the product, customers, user and

various other subject matter experts about their opinion about the requirements. It’s always possible

that all the requirements may not be in your brain and you need a different perspective for better

understanding the project and interviews give you that opportunity. It enables you to gather a large

amount of information in a quick time and is also a quick method to implement. There can be two

types of interviews - structure and non-structured.

Benefits: When we talk to someone and understand their needs and knowledge on a personal level,

we can make sure that we are recipient of the real situation and not just the perceived situation

Disadvantage: They can be time consuming because one needs to set it up, analyze it, feedback,

reporting etc. and this can cost a huge amount.

3.Prototyping

This method is fairly new as compared to others wherein we try and gather the basic information

needed as requirements and form a sort of clarification which we term as a prototype. Its importance

is that is assists business analysts in deciding whether the path chosen, shown by the prototype is

good and in accordance with the stakeholder's demand or not. If not, then necessary changes can

also be suggested by them so that these changes can be implemented.

Benefit: It helps us in gaining confidence that whatever we are doing is in accordance to the

stakeholder ideas.

Disadvantage: It tends to increase the complexity of the system as designing and redesigning can

go on and on and become a tedious task.

References:

Showing Page:

3/3

Unformatted Attachment Preview

Kodie Turner CS349 5/6/20 In software engineering, we need to be clear about the requirements about the project before we dive deep into its formatting and development. The part where we do research and discover the requirements of a system from user's perspective, customer’s perspective and from the eye of other stakeholders. The segment where we allocate the practical requirements of system is a vital cog in the development of project. If its overlooked, the project can turn haywire with the time and spending plan and could lead the team into a fizzled project. Keeping in mind that there is not one single technique that suits all the scenarios, let us discuss three different elicitation methods: 1.Brainstorming To generate ideas around a specific domain, we need to have planned brainstorming sessions. It is the method where a group of people with their own set of ideas and imaginati ...
Purchase document to see full attachment

Tags: software engineering prototyping project development software software development