Question 1


Disadvantagesof Waterfall Model

Once a given step is completed, it is very hard for the developers togo back to the previous stages and make any changes and thus, themethod is reliant on the initial requirements. It, therefore, meansthat if these demands were faulty, the project could not continue.

Another disadvantage of waterfall method is that when a bug isestablished, or changes are needed. Ultimately, testing of theproduct is made at the end, and if errors are found, their existencemay affect the whole project, and thus a project developer may betempted to delay a thorough testing, and this delays may allowshort-term wins

Agileaddress those disadvantages

The agile method is used to allow for the changes in the preliminarysetup. It writes the program again as the client makes the decision.Since this methodology allows for changes to be made, it is,therefore, easier to add some entities that will keep the userupdated on the latest industry development. Thus, in the end, thepriorities of the project are examined.

Useof Agile

Agile can be utilized when a rapid production is more important thanthe product quality. It can also be used when the customers will havethe capacity to change the project scope. Also, it can be utilizedwhen there is no clear picture of the final product. It can also beused when there are skilled developers who are able and adaptable tothink autonomously. It can be used when the product is intended for achanging industry.

Question 2

FiveDuties of System Analyst in Software Project Management

  • The functions of a system analyst are to assist an organization to comprehend the challenges before them to ensure that the expectation and needs of the clients are correctly represented in the final solution.

  • The analyst takes the responsibility of ensuring that the set requirements are documented and captured correctly before a solution is implemented and developed.

  • The analyst might be regarded as the business analyst in some companies and may take the duty of a requirement analyst.

  • Once the analysis phase, the analyst ensures that the overall project meets the needs of the clients.

  • The system analyst understands and analyzes the current State process to make sure that project team and customers comprehend the implication and context of the change

  • The system analyst’s also understanding and develops how future and present needs of business will impact the solution

Prototypeand its uses in Requirement Gathering

The prototype is a simulation or a model of a real thing. In systemanalysis, a prototype is described as the system model or asubsystem. A system is anything that can range from the air trafficcontrol system to food ordering system. The prototypes of this systemtake various shapes. It can be computer or paper-based. Therefore,prototyping is the process used to develop the prototypes. It is asupplemental methodology. Therefore, a prototype is used to gatherrequirements and thus are useful in visualizing the feel and look ofthe process and application workflow. The useful life of a prototypevaries based on the lifecycle model of the project. Therefore,prototype is used as the basis for developing the final solution

FourBenefits of Viewing the Organization as a System

The advantage of viewing the organization as a system is thateducators, writers and consultants are assisting the managers inseeing the team from a wider perspective. Another advantage is thatsystem theory brings a new perspective for managers to decode eventsand patterns in their organization. Thus, managers can recognize thevarious organization parts particularly the coordination of officersand the interrelation of different parts. Managers can now focus onthe matters of feedback and ongoing organization. The managersdiagnose the problems by recognizing wider interaction patterns.Finally, the managers can focus more solidly by emphasizing on theoutcomes they want from their organization and thus can focus onstructures that inflame behaviors determining events

UseCase vs. Process Modeling and Requirement Determination

Use case designing is used widely in modern software development asan approach for unfolding the requirements for a given software. Fromthe use case, it is feasible to scrutinize other representation atthe similar abstraction level as well as lower-level representation.Since the usage is a description of the requirements, it describes anexternal view of the system. Use cases are related to requirementdetermination since much work has been harnessed in both to show howmodels of different types are derived from each other. Process model,on the other hand, is used to prepare use case model to design theneed for the user.

Question 3

Question 4

Differencesbetween Functional and non-Functional Requirements

Its description centers on functional requirements based onanticipated performance of the system or product to be formed. Thefunction is equal to the system/product features for which you mighthave a button or menu choice such as selecting an order, identifyinga customer or calculating the amount due. Examples: Set up anaccount, downloading the mobile app, enter pickup location andcustomer signup

Nonfunctional requirements on the other hands are the attributes suchas security, performance level, and reliability, usability andavailability. Definers are wrapped in how the system/product isexpected to lose sight and function. When these factors are notaddressed sufficiently, the system functioning will fail. Forinstance, the system may identify customers in such an insecure, slowand complicated manner in that it can cause mistakes that provokefrustration. Examples include: Billing the fare automatically billedto credit card and Provide feedback

Categoriesused to decide the best software vendor.

  • First, the organization need is documented to assist in making a decision.

  • Potential source is identified to see the team that can best do the job

  • Initial discussions with vendors where potential service provider come to site and describe their offerings and how they will meet the needs

  • Weeding out vendors and getting down to reasonable 2-3 final vendors to discuss

  • Final vendor round to help the finalist make their offer stick to win the business

  • Decision is made based on ability and cost to meet the requirements

JAD preparation by System Analyst

JAD is a structured process where analysts, managers, and users workfor several days in an array of intensive meetings to review andspecify the requirements. The system analyst stays in session untilthe objectives are completed, documented and agreed

Stepsin Iterative Project Lifecycle

  • Planning the project by defining and describing procedures such as issues, risk, scope, quality, and communication

  • Analysis focuses on the main functions and features to be delivered

  • Prototyping utilizes the requirements receiving in previous steps

  • Repeat prototyping and analysis by updating the prototype to present the set of requirements

  • Conclusion of prototyping by formal user acceptance testing and full system testing

  • Implementation of the prototype


McCormick, M. (2012). Waterfall vs.Agile Methodology.&nbspRetrievedFebruary 12, 2014

Dennis, A., Wixom, B. H., &ampTegarden, D. (2015).&nbspSystemsanalysis and design: An object-oriented approach with UML.John Wiley &amp Sons

Singh, A., &amp Sharma, E. S.(2014). Functional Test Cases Generation Based on Automated GeneratedUse Case Diagram

Chung, L., Nixon, B. A., Yu, E., &ampMylopoulos, J. (2012).&nbspNon-functionalrequirements in software engineering&nbsp(Vol.5). Springer Science &amp Business Media