BSA375_Week2Discussion_post1_2023

One traditional way of determining system requirements during analysis is interviewing.

This involves talking to with users about current or potential systems to establish needs.

These interviews can be done individually or in a group setting. Conducting interviews in a

group setting may allow you to see requirements from multiple sides at once, since users can

agree/disagree with each other in a group setting in real time. A contemporary technique is

prototyping. Prototyping can be used to gather user requirements and present them a

working system prototype. This can allow users to test the sample system and analysts can

then adjust the prototype to properly fit the user’s needs .A radical method of determining

system requirements is business process reengineering (BPR). BPR is the search for and

This method is useful when detailed insight into the system requirements is needed. A

drawback of the interviewing technique is that it is time-consuming and can increase the

duration of the information systems project. It can be used when the needs of the users might

vary. A contemporary technique for determining systems requirements during analysis is

called prototyping. The prototyping method can be used for capturing user requirements and

then presenting them as a working system prototype. It is most useful when users need to get

involved in the design process and ascertain whether it is aligned with their needs or not . A

drawback of the technique is the absence of a methodical process. It is possible to ascertain

whether to use the technique or not if users find it difficult to specify their exact

requirements. Process modelling is a radical technique for determining systems requirements

during analysis. It involves a graphical representation of the process, which can be used to

get better clarity into system needs .A drawback of the technique is the risk relating to

excess analysis. The decision to use the technique depends on the need to understand the

existing system. One traditional way of gathering and documenting requirements is through

a use case. A use case is textual description of a user (an actor) using or interacting with a

system. We establish a goal -- what the user wishes to accomplish and write out the steps

(scenario) in which the user will perform actions to accomplish the goal. We can also

document pre-conditions and post-conditions, which describe what must happen before the

scenario can begin and the conditions that follow upon the scenario completing. This is a

which means it will lay out the steps in order and meet all the requirements and all the

stakeholders are involved. Most organizations are familiar with these techniques so they can

utilize more effectively and in a controlled manner. Once an organization have a clear

understanding of problem and the requirements will be the most beneficial technique to

employ. And of course, this might take more time and lots of documentation which can be

helpful for future references. The advantage of contemporary technique is that is user

cantered focused which means this will put a strong emphasize on user requirements and

their needs. With these techniques it also fosters more collaboration between users,

stakeholders and other teams to meet all the requirements. This technique can adapt to any

situations by quickly develop prototypes and test any issues in which they get feedback. The

Radical technique is faster way for determine the requirements with new innovation and

experiments. With this approach developers can come up with quick solutions and get quick

feedback to reduce time and cost. This technique is also emphasized on user involvement

which can create effect solutions. Based on all these techniques, I would use traditional if I

know what my problem is and I have the solution that will solve everything. This type of

method is for organizations that needs more faster functional requirements to meet their

functional requirement. For contemporary techniques is for organizations that are more user

orient system. Their goals is how to improve the user interface for better system. The radical

techniques is much faster approach in my opinion because it allows the organization to get a

sent out to everyone. In the interview process, other questions come up and more details are

recorded. Interviews would be recommended when the topic of the interview isn't so black

and white, but maybe has a lot of gray area. A contemporary method, Joint Development

Application (JAD), is a common business analysis technique. JAD is a process that involves

the client to design and develop computer-based systems. Some advantages include lower

risks, better software with minimal errors, accelerated process and lower costs. Some

disadvantages could arise from different opinions and time issues. JAD would be good to

use when a client is looking for something new and unique. Finally, Business process

reengineering methodology, a radical process, is defined as a process that takes areas

important to a customer and rethinks and redesigns to achieve a dramatic improvement. This

allows a business to focus on customer needs or whatever else they deem important. It also

can get rid of unnecessary activities. Disadvantages can be that it isn't good for every

business and other department could end up suffering from the "improvements" in other

areas. One tradition way is for finding the system requirements is ask someone that has

ready done a similar project before. This is effective and can save a lot of time. A more

contemporary style would be to ask AI or some other sort of learning system to do it for you.

This will eliminate human error. A more radical process would be get a bunch of options

and put them in a hat and choose from the drawing of the hat. This obviously is the least

recommend option. The drawbacks of asking someone else is that their ideas may not be

problems and opportunities and what is needed and desired in future systems. Typically, the

current way of doing things greatly impacts the new system. In some organizations, though,

management seeks new ways to perform everyday tasks. These ways may be radically

different from how things are done now, but the payoffs may be enormous: Fewer people

may be needed to do the same work; relationships with customers may improve

dramatically; and processes may become much more efficient and effective, all of which can

result in increased profits. The overall process by which current methods are replaced with

radically new methods is referred to as business process reengineering (BPR). To better

understand BPR, consider the following analogy. Suppose you are a successful European

golfer who has tuned your game to fit the style of golf courses and weather in Europe. You

have learned how to control the ball's flight in heavy winds, roll the ball on wide-open

greens, put on large and undulating greens, and aim at a target without the aid of the

landscaping common on North American courses. However,BPR advocates suggest that

radical increases in the quality of business processes can be achieved through creatively

applying information technologies. BPR advocates also suggest that radical improvement

cannot be achieved by making minor changes in existing processes but by using a clean

sheet of paper and asking, "If we were a new organization, how would we accomplish this

activity?" Changing how work is performed also changes how information is shared and

stored, which means that the results of many BPR efforts are the development of

(JAD), a contemporary method, is a very common technique in the business analysis world.

It brings system developers and users together in a productive and creative environment

through a structured approach that involves discussion groups with the goal of obtaining

requirements and specifications. The advantages are that it allows you to resolve difficulties

simply and produce better, joint collaboration between the company and clients lower risks,

reduces costs and time needed for project development, and has well-defined requirements

to improve system requirements. Some disadvantages are that different opinions within the

team can make it difficult and depending on the size of the project it may require a large

time commitment.Business process reengineering methodology, a radical methodology,

involves the radical redesign of core business processes to achieve dramatic improvements

in productivity, cycle times, and quality. The advantages are that it gives an appropriate

focus to business as it revolves around customer needs, it helps in building a strategic view

of operational procedures by making radical inquiries about how processes are improved and

how things could be done, it eliminates unnecessary activities and thereby helps in reducing

organizational complexity. Some disadvantages are that it doesn't suit every business need as

of one department is improved at the expense of the overall process. There are some pros

and cons when it comes to a traditional, contemporary, and radical technique when

determining systems requirements during analysis. For a traditional approach, I think

A contemporary technique could be use is the Joint Development Application (JAD). This is

a typical method in business examination environment. This brings clients and system

developers together in an organized methodology that includes discussion groups with the

objective to acquire necessities and determinations. A disadvantage is that various beliefs

inside the group make it hard to adjust objectives. However, JAD permits you to resolve

difficulties more simply and produce better software. I would use this technique when the

organizational culture underpins joint critical thinking practices among various degrees of

employees.As for the radical technique, I would consider the Business process re-

engineering (BPR) methodology. An advantage of this is that it gives proper concentration

to a business as it rotates around client needs. A disadvantage is that it does not exactly suit

each business need as it relies upon factors like size and accessibility of assets. I would use

this technique when companies need to break the mold and turn the tables in order to

accomplish ambitious goals. There are several factors to consider for each IS project to

consider which technique(s) to employ during the determination of systems requirements for

the analysis phase. One may use a more traditional approach such as interviewing everyone

from the users on up to the stakeholders to determine system requirements, but the drawback

is the time and need for interpersonal skills and organizational meetings. The more

contemporary approach is the e-JAD or electric joint application development method in

which the client and developers along with a facilitator iron out the system requirements in a

lesson focuses on the analysis phase of the Systems Development Life Cycle (SDLC).

During the analysis phase, determining the requirements of the system that is being

developed is integral to the success. The different techniques that can be used during this

phase include: traditional, contemporary, and radical. Traditional methods include

interviews, document analysis, and observations. Interviews can be conducted using a top-

down approach, which can be a more effective when it comes to gathering information.

Contemporary techniques are based on a bottom-up approach and allow for more

collaborative, for example the Joint application development, or JAD, brings stakeholders

together in a group workshop setting to identify the system requirements. The downside of

this can be reluctance or resistance to change, as well as lack of participation. Radical

techniques allow the stakeholders to be more directly involved in designing, via active

participation. In this way, stakeholders can confirm that the system is satisfactory. I believe

the approach an analyst decides to take will depend on the system that needs to be designed.