Running head: &nbsp 1



June31, 2014.

Meaningof analysis and Purpose in System analysis and Design development

Analysisin this context means the process of investigating a system,identifying the weakness or problems, identifying improvementopportunities, planning and developing an approach to design and makea new system. Analysis is critical in that it guides the projectsteam in strategizing new ways of designing another system bygathering information that is used to form a model that is thenpresented to the project sponsor for confirmation.

Elementsof System proposal

Theseinclude technical feasibility of the design project, the economicfeasibility and the organization feasibility. In general, a systemproposal encompasses the whole process of project analysis in termsof plan, design and implementation.

Differencebetween business, user, and functional requirements

Businessrequirement refers to the reasons why a new system would benefit theorganization the value that are associated with the system. Businessrequirement entails the efficiency of the system to serve the purposeits design for for instance, improving customer online interactionswith customers. A functional requirement is the ability of a newsystem to improve efficiency the features incorporated in thesystem. User requirements on the hand refer to the business valueexpected by the user both in tangible and intangible form i.e.reduced operation cost and ability to improve customer service.


Functionalrequirement refers to the features that the system need to have. Inthis case, functional needs relate to the characteristics that thesystem has that help in supporting and performing of users’ tasks.For instance, if the user wants a system that can ‘schedule for anappointment with the client,’ and ‘confirm appointment,’ thenthe feature of the system needs to be designed in that way.

Nonfunctionalrequirements of a system

Nonfunctionalrequirement refers to the essential behavioral qualities thatsoftware should have like usability and its performance. In otherwords, non-functional requirements are those external attributes indesign or implementation that particular software need to have.Primary types of non-functional requirements include the hardware,software or other necessary architectural features of the system.Assessment of non-functional requirements of the system helps inmaking design decisions and other major issues during the designphase.

Stepsof the analysis process

Theanalysis process entails three processes that include understandingthe existing situation of system, identifying the areas ofimprovements and defining plans and needs for a new system. In mostcases and some projects the first process is assumed or done in asimplistic way in situations where no system exists. In other cases,the process steps are skipped if they are not necessary whendesigning future software’s or the project team is using adifferent version of development methodology.

Considerationsmade when determining who to include in interviews and JAD sessions

Oneof the key consideration issues made by the analysts of systemdevelopment is the effectiveness of the chosen person’s opinion,important stakeholders who are affected or can influence the systemdevelopment. In this case, customers, managers and employees areconsidered. In addition, consideration is done on other relevantindividuals who might significantly influence the implementation ofthe project after completion.

Stepsin conducting JAD sessions

Theinitial step of conducting JAD involves the selection of interviewparticipants and the JAD facilitator. The selection process isfollowed by designing the JAD sessions in regard to the length oftime needed for the interview sessions. The third step is preparingthe participants and the analyst for the sessions to enhance them isconversant with the system development issues. In the fourth step,the JAD session is held in which the facilitator manages thesessions. Afterwards, the final step involves the post JAD follow-upin which the session is arranged to facilitate in gathering moreinformation.


Documentanalysis helps the project team to understand more about the existingsystems and other emerging issues. These documents are important inproviding useful information about formal and informal systems thisis essential to the project team in identifying which areas need tobe changed.Documentanalysis is also essential in that, it helps to reviewrecommendations made by other analysts in regard to the system thisis an important aspect for most system designers.

Problemanalysis as an analysis strategy

Theproblem analysis is an effective analysis strategy because the systemanalyst gets good ideas from the users on the changes that need to beimplemented in the new systems. The strength of this strategy is thatit helps in improving the systems on an incremental basis. However,this method is not effective because it inhibits capitalization ofopportunities and provides minor improvements. In addition, theimproved systems lack monetary benefits.

Rootcause analysis as an analysis strategy

Inthis case, the analyst relies on their problem assessment skills tomake assumptions of issues that need to be changed. Its main strengthis that, with good problem analysis this technique leads tosolutions. However, these technique leads to wrong solutionsespecially if the users give information that have not been carefullyassessed. This results from the fact that, many users give symptomproblems rather than the root cause problems.