1.Tony Carolla Dec 7, 2022 at 6:48 AM Hello Class, It is critical to identify al
Place your order now for a similar assignment and have exceptional work written by our team of experts, At affordable rates
For This or a Similar Paper Click To Order Now
1.Tony Carolla
Dec 7, 2022 at 6:48 AM
Hello Class,
It is critical to identify all requirements for a project at the beginning. It may be tempting for a developer to look at a project problem statement and assume that they know what the stakeholders want exactly, but each situation is different. It is best to identify the product needs by asking the customer for specifics.
There are many ways to solicit information from users about a project. The techniques used will depend on the project size, the organization size, and the organization’s culture. At my employer, I produce software for the organization, so the customers are my co-workers. We use several techniques to gather requirements, including email, online chat, and meetings.
The main modes of elicitation are verbal, written, and online (Tsui et al., 2018). Verbal meetings are an excellent way to discuss the project interactively. Project discussions involve a lot of back-and-forths, and if it is handled via email, it may take a lot longer. Taking good notes during these meetings and capturing valuable information is critical. Written or online elicitation may be necessary for large projects or if it will work better with the organization’s culture. These forms of elicitation allow the requirements analyst to think through the questions carefully, and they should be followed up by a verbal meeting (Tsui et al., 2018).
When eliciting information for a project, there are many categories of information to capture (Tsui et al., 2018).
Opportunity and Needs: What problem should the project solve?
Justification: How will the project pay off for the organization?
Scope: Which areas of functionality will the project solve?
Major Constraint: Any major requirement or constraint, such as a deadline.
Major Functionality: What are the most important functions the project will solve?
Success Factor: What must transpire for the project to be considered a success?
User Characteristics: What type(s) of users will be served? Internal, external, or both?
All this information must be captured and organized. The seven categories of information fit into the following six dimensions of project requirements (Tsui et al., 2018).
Individual Functionality: The specific functions needed by each group of users.
Business Flow: The ways the functionality works together to accomplish the organization’s goals
Data, Formats, and Information Needs: What information will be coming into and out of the system?
User Interfaces: How will the users interact with the system?
Other Constraints: How will the project be constrained for performance, reliability, and security?
Systems with Other Interfaces: What other systems will interface with the new system, and what are the details of the interfaces?
-Tony
2. Jaime Aviles
Dec 7, 2022 at 6:45 PM
Greetings class,
First, let’s start with identifying the elicitation modes, categories of information, and constraints. The excitation modes are the manner in which the developers acquire the system’s needs and desires. These questions are presented either verbally, written, or in an online form. The categories of the requirements include software’s justification, needs, scope, major functionalities, success factors, user characteristics, and major constraints. The constraints typically are the allotted budget for the project and the schedule to deliver the software to production (Tsui, Karam, & Bernal, 2018).
Scenario
While at work, my team and I receive requests to set up an automated process to a manual procedure that may take our quality assurance team hours to perform. Recently, we were asked to create a process that logs into two individual servers and checks for specific “30016” error codes. If any codes are found, we are to format the output and create an incident ticket to be tracked. To elicit the software requirements, we had a team meeting consisting of all stakeholders, developers, and documentation staff. I am the primary coder, so I asked the stakeholders about the primary goal, which is mentioned above. Once that information was documented, I wanted to know how the formatting was and if they needed any further details. Next was to ask them how often this error check was supposed to take place, the operating system the servers are using, what are the necessary credentials to log into the machine, and what file formats we will be working with. The last portion is to have the requester fill out an onboarding task ticket so that it can be assigned to our team. Using the six dimensions of requirements, the following was determined:
Business Flow: Every day, Sunday through Saturday, every three hours starting at midnight Eastern Standard time.
Individual Functionality: Since the process will be using cronjobs, no specific individual functionality is needed.
Data, formats, and information needs: Special proprietary files structure provided by a third-party vendor will be parsed. Linux Bash is the interface; only lines containing the error code “30016” are needed.
Constraints: To log into the server, we will need infrastructure to install the provided security key in the authorized keys section of the secure shell file directory. This will provide security from man-in-the-middle attacks when logging into the servers. All processes must be done on the virtual private network.
User interface: The developer interfaces will be Red Hat Linux 7 and Comcast’s Gears platform for automation. The user interface will be the ServiceNow ticketing system.
Systems with other interfaces: No other systems will be involved.
The team was given until the end of the 2023 first quarter. All documentation will be discussed with our technical integration team so they can create a wiki page for the process. Any further questions will be brought up to the lead supervisor and primary lead of the request.
3.Cody Angeline
The goal of any software process model is to systematically coordinate and control software development(Tsui et al, 2018). Modern software models evolved from rigid frameworks whose major shortcomings were a lack of task overlapping, and limited customer interaction with theproducts developers. These shortcomings increased the risk that a development team would be unsuccessful in delivering a useful product to their customers. This risk produced incremental process models whose focus became flexible iterations and heavy customer involvement. Incremental process models are better than traditional approaches for systems whose requirements are likely to change during the development process.
Traditional Model Evolution
The first software process model to be published was the waterfall model. This model took themes used in the design of military systems and applied them to software. In waterfall, software development is completed in stages and cascades from one phase to the next. Each stage of the waterfall method reflects the fundamental software activities of requirements engineering, software design, implementation and unit testing, integration and system testing, and operation maintenance. Over time, the rigid approach proved more useful in traditional engineering endeavors and less useful in a software environment; were customer requirements tended towards frequent change. This led to modifications of the process such asadditional iterations over the project, and inclusion of the user during the design and maintenance phases of development (Tsui et al, 2018).
Out of the modifications made to waterfall emerged incremental processes. Incremental models utilized a divide and conquerapproach to development in which tasks were subdivided into smaller components. This proved to have some risk aversion benefit because the first increment could be delivered as a release. Development could overlap and be performed sequentially allowing for a quicker product turnaround.The difficulty with this model arose from the tight coupling that generally exists within problem domains. Task proved difficult to reduce into independently implementable components without a prior understanding of the problem domain during the requirements elicitation (Tsui et al, 2018).
Spiral Model
As incremental development evolved,a model called spiral came into use. The spiral model was largely risk adverse and applied cycles to incremental development. Each cycle of a spiral begins with the identification of a component of the product being produced, the alternative means of implementation, and design constraints that have been imposed on the alternative implementations. Once risk has been completely evaluated, the next phase moves to develop a prototype in an effort to continue to analyze the implementation risk. If the prototype proves to be operational, the subsequent phases follow the basic waterfall approach incorporating incremental development norms. Each level of software specification is then followed by validation and preparation of plans for the succeeding cycle (Sommerville, 2018).
Agile Processes
Agile methods are incremental development methods that produce software releases over short iterations. The foundations of Agile processes are rooted in a document called the Agile Manifesto. The Agile Manifesto states that in order for a development method to qualify as Agile it must implement these maxims: incorporate customer satisfaction, be open to change, deliver working software frequently, put people first, build projects around motivated individuals, utilize face-to-face meetings, measure success based on working software, maintain a constant pace, have attention to detail, maximize simplicity, form self-organizing teams, and be reflective (Agile Manifesto, 2001). These maxims proved to be extremely useful in competitive business markets.
Conclusion
Traditional process models closely followed the fundamental software development activities. Although models such as waterfall proved useful in traditional engineering efforts, it failed to be flexible enough to adapt to changing customer requirements. Incremental development emerged as a result of modifications that were made to traditional waterfall development processes. Risk became a driving factor for a project’s success, and because of this spiral development became favored. As the need for flexibility and rapid releases increased, Agile processes grew in popularity because of their customer centric workflows.
4.DaLynn
Introduction
In the realm of software development, not only is it important for all roles of the project to know what they are responsible for,but it is also important to choose the proper methodology that will be utilized to implement the new software. There are many specific tasks that must get accomplished during the software development lifecycle andbased on a team’sexperience and the type of application work that is being asked, it is important to choose and utilize the best fit as it relates to the methodology. Process methodologies are there to guide a development team and its members to coordinate and accomplish all task that must be performed to achieve valuable, workable software for the stakeholders (Tsui, Karam & Bernal, 2018). As noted previously, it is important to understand each methodology and its limitations while choosing the proper and most effective method.
Agile Process Methodology
You will hit challenges when it comes to software development. The challenges that can come about and should be mitigated via methodology are time management of a project, change management, and communication to name a few. The agile methodology is a process method to would on exercising an incremental development cycle (Geeks for Geeks, 2020). The agile methodology also allows for fast and prompt responds to change management. Software developed utilizing the agile methodology is provided to the customer in small increments and they can see their concepts quicker and respond with changes in a fast-paced environment. Additionally, stakeholders and users are in constant communication with the development team throughout the process so communication of every aspect of the project gets reviewed daily. All in all, this approach allows for clear communication, quicker deliverables, and faster ability to accept changes and implement them.
Limitations of Waterfall Methodology
The waterfall methodology, which is a traditional methodology that has been utilized since 1970 (Martin, 2022). The waterfall methodology is a model that works in a specific sequence. Each phase of the method must be completed prior to moving to the next phase. Waterfall consists of the following phases: plan, requirements, design, implementation, test, and maintenance. As with any procedure or process, over time, this methodology has become outdated and consists of various limitations. Below I have outlined some of the main disadvantages of the waterfall methodology (Martin, 2022):
• Not suitable for requirement changes
• Requirement documentation is time consuming.
• Stakeholder/user are not involved in all phases of the lifecycle.
• Longer timeframe for delivery of working software
• Defect discovery and resolution is slower and later in software phase.
Conclusion
In conclusion, while preparing for a project where you are developing software applications, understand the advantages and disadvantage of the software methodologies and methods offered to follow the software development lifecycle. There is no wrong approach but choosing the most efficient methodology will warrant happy stakeholders receiving value add software that is provided to them in a timely manner with little to no defects. It is essential for delivery of a successful project and deployment of the project to select the best development methodology.
Place your order now for a similar assignment and have exceptional work written by our team of experts, At affordable rates