+1 (208) 254-6996 [email protected]
  

Assignment Content

  1.     As you learned in Wk 2, requirements are a fundamental component to any project. Depending on the SDLC applied, requirements can be written in different forms. For example, some requirements will be very technically focused (technical requirements) and are written in a manner that dictates what a stakeholder expects the system to accomplish. Another approach taken, often with Agile-run projects, is to create a user story. A user story focuses on different types of system users and outlines more of a workflow that organizations expect.


    Review the Wk 2 Discussion – Project Requirements about what are considered well-written requirements.


    The WeLoveVideo, Inc. project team met with the business owners last week in a structured requirements-gathering meeting. In this meeting, they discussed that the requirements should focus on certain users, such as customer support representatives and inside-sales representatives, as well as be geared toward the system supporting the job function.


    Create 15 to 20 system requirements based on the scope of the project discussed in the requirements meeting. Ensure the requirements meet quality standards and are outlined in priority order. Provide a justification behind the prioritization within the document. You may use any Microsoft® program, such as Excel® or Word, to create the list of requirements.


    Submit your assignment.

6

Wk2- Apply: Signature Assignment: Project Plans

Don't use plagiarized sources. Get Your Custom Essay on
Wk 3 – Apply: System Requirements [Due Mon]
Just from $13/Page
Order Essay

Examining the Project plans in both waterfall and Agile to Help the CIO understand the implications of the SDLC Frameworks to her team

Student’s Name

Professor’s Name

Course Title

Submission Date

A Representation of a Milestone-Level Project Plan for Welovevideo, Inc.’s CIO Using the Waterfall SDLC

C:\Users\IRENE-PC\Downloads\Milestone-level project plan using the waterfall SDLC.jpg

In the waterfall SDLC model, each phase must be completed before proceeding to the next phase. This framework is accurate for WeLoveVideo Inc. but its selection is based on factors like deadline and the budgeted resources for the project. With the waterfall approach, the entire process will be broken down into separate phases. The results of every stage are considered as contributions to the proceeding one. Hence, the company’s CIO should note that each stage of interaction for progress begins exactly when the last stage is completed. The inputs, milestones and waterfall SDLC phases for WeloveVideo Inc. would include the following:

Requirements : This phase will encompass determining the requirements to be planned and their capacities and their respective rationales. Some inputs for this stage that WeloveVideo Inc. CIO need to consider for the company’s CRM project include contact animation tools, tracking tools, communication tools, and integrative support subsystems. The data for information and the results for this step are taken into account and stamped.

System design: In this phase, the required data from the initial phase is concentrated and the framework configuration is ready. The frame design helps the developers identify frame equipment and requirements and also helps characterize the overall system development. The product code that will be written in the next step is created in this phase.

Implementation: With the help of the master plan from the developers, CRM systems will be developed slowly but continually, starting from sub units, which will be integrated in the next step. Each unit is created and tested for usability, which is known as unit testing and the CIO will need to understand the deliverables of running every unit test and the modules associated with the next steps.

Integration and testing: All units created during the implementation phase are coordinated within the framework after each device is tested. The planned product must go through sequential development to see if there are any defects or errors, which WeLoveVideo’s CIO should be acquainted from the developers’ advice and their expectation. The inspection is carried out in such a way that the CIO has no problems in making the product.

System’s Use: After meaningful and practical testing, the CRM will be transferred to WeLoveVideo Inc.’s environment where it will be deployed and utilized to meet organizational goals.

Maintenance : This development occurs after establishment and includes adjustments to the system or separate sections to change credits or develop further performance. These adjustments are made either based on customer-initiated progress requirements or deformations detected during use of the active framework. The CIO will receive simple support and assistance for the programming created. Figure 1 reflects key deliverables from every phase of the waterfall SDLC that the CIO should consider and expect.

A Representation of a Milestone-Level Project Plan for Welovevideo, Inc.’s CIO Using Agile SDLC

C:\Users\IRENE-PC\Downloads\Agile SDLC Plan,,.jpg

The agile SDLC is an organized sequence of phases that elements go through from start to finish, consisting of six phases: concept, inception, iteration, release, maintenance, and retirement. The Agile process will change slightly depending on the efforts that the developers will have put and the final functionality. Scrum groups, for example, will work in short periods referred to as iterations which act like sprints. The inputs, milestones, and phases that the CIO of WeLoveVideo Inc. should consider are as follows:

Concept : Here the CIO, being the company’s representative for project development process will decide the scope of expropriation. If there are different activities, then the CEO will have to focus on the most important ones.

Inception: Once the idea is illustrated, it becomes time to form a product improvement team. The CIO will then check the availability of their staff and select the best people for the business while providing them with essential equipment and assets. For instance, the officer can start interacting with the plan, team’s model user interfaces and create architect tasks.

Iteration: Next is the cycle phase, also known as development. In general, this will be the longest leg because this is where most of the work is done. Engineers will work with UX initiators to tie up all prerequisites for item and customer delivery and turn plans into code. The goal is to collect the found benefits of the item before the end of the main cycle or mileage.

Release: The quality assurance team needs to carry out certain tests to ensure that the product can really be used. These agile team members are ready to test the framework to make sure the code is flawless if any possible errors or deformations are identified, the engineers will fix them right away. This is also where the CIO preparation takes place, which requires more documentation.

Maintenance: The product is currently fully transported and available to customers. This activity moves it to the maintenance phase. During this phase, the product improvement team provides ongoing support to keep the framework running as expected and to fix new bugs. They will also be around to provide additional training to CIO and other system users to ensure that they are comfortable using the system. In the longer term, new focus could be placed on reviving the current position through redesigns and additional provisions.

Retirement: There are two reasons why a product enters the retirement phase: Firstly, it can be replaced with a new program or framework that may actually expire or is permanently incompatible with the organization. The product improvement team will first notify the CIO and the entire WeLoveVideo Inc. system’s users that the product is out. In the event of a replacement, the company will be migrated to the new system and environment. Therefore, as picture 2 reflects, the agile SDLC framework is more suitable for the company based on the deadline, the deliverables, and the expected users.

References

Olorunshola, O. E., & Ogwueleka, F. N. (2021). Review of System Development Life Cycle (SDLC) Models for Effective Application Delivery. In Information and Communication Technology for Competitive Strategies (ICTCS 2020) (pp. 281-289). Springer, Singapore.

Shaikh, S., & Abro, S. (2019). Comparison of traditional & agile software development methodology: A short survey. International Journal of Software Engineering and Computer Systems5(2), 1-14.

Wk2

Apply: Signature Assignment: Project Plans

Examining the

P

roject plan

s

in both waterfall and Agile

to Help

the

CIO

understand the

implications

of the SDLC Frameworks

to her team

Student

’s Name

Professor

s Name

Course Title

Submission Date

Wk2- Apply: Signature Assignment: Project Plans

Examining the Project plans in both waterfall and Agile to Help the CIO understand the

implications of the SDLC Frameworks to her team

Student’s Name

Professor’s Name

Course Title

Submission Date

Order your essay today and save 10% with the discount code ESSAYHELP