logo

System Analysis 14 System Analysis Name Affiliate Institution

   

Added on  2020-05-11

14 Pages2632 Words104 Views
Running head: system analysis1system analysisNameAffiliate Institution
System Analysis 14 System Analysis Name Affiliate Institution_1
Running head: system analysis2Table of ContentsIntroduction.................................................................................................................................................3Extreme Programming (XP)........................................................................................................................3Extreme Programming Values.....................................................................................................................3Extreme Programming Life Cycle...............................................................................................................4Extreme Programming Practices.................................................................................................................6Feedback of fine-scale.........................................................................................................................6Continuous process..............................................................................................................................6Shared understanding..........................................................................................................................7Programmer welfare............................................................................................................................7Conclusion...................................................................................................................................................8Event Table for Comfort Quilts Limited......................................................................................................9Domain Model Class Diagram Comfort Quilts Limited............................................................................10Design Class Diagram Comfort Quilts Limited.........................................................................................11Use Case Diagram Comfort Quilts Limited...............................................................................................12Use Case Description................................................................................................................................12Reference list.............................................................................................................................................13
System Analysis 14 System Analysis Name Affiliate Institution_2
Running head: system analysis3IntroductionExtreme programming (XP) is the most suitable adaptive methodology that will help ComfortQuilts Limited to develop a system that will deal with their issues such as managing applicationsfrom their suppliers, and running reports on individual purchases and individual shipmentsmethod. In this context, XP is well defined and its values, lifecycle and practices outlined.Extreme Programming (XP)XP is a development methodology of a system structured to improve system quality and itsability to cope properly with changing requirements of the client. The objective of extremeprogramming is to provide small releases that are frequent and iterative throughout the project.This allows customers and team members to review and evaluate the progress of the projectthroughout the whole system development life cycle (SDLC). As such XP will help ComfortQuilts Limited to carry out reports on small purchases, shipping methods of their products and beable to analyze whether the new project will be effective. (Stephens & Rosenberg, 2003)Extreme Programming ValuesXP methodology consist of five important values that offer the foundation on which the ExtremeProgramming wholeness is built. These values allow involved team members to be confident onthe direction of the project and to understand the importance of individual feedback and insight.Simplicity: this value allows the team members to carry out what is requested and needed andnothing more. This maximizes created value for the investment generated to date. The involvedteam perform small easy steps to their objective and eliminates failure as they occur. The teamensures they build something commendable and facilitates its maintenance for long term at acheaper cost. (Becker, 2010).Communication: everyone involved in the project of building the system is part of the team.Communication within the team should be face to face on a daily basis. They should work inunison from requirements to code. (Lassenius, Dingsøyr & Paasivaara, 2015)
System Analysis 14 System Analysis Name Affiliate Institution_3
Running head: system analysis4Feedback: the team should be committed on every iteration by delivering a system that isworking. The team should display the system early, then listen carefully and modify any changesthat might be needed. The team should ensure they adapt to the processes.Respect: team members should maintain respect among themselves. Everyone should feel valuedand offer value. Respect should be enhanced between the customers and developers. In addition,the management should also show respect to the developers right to agree on responsibilities andaccept authority over their work. (Abrahamsson, 2008)Courage: the team should be truthful on project estimates and progress. They should also avoiddocumenting failures as the plan set is to enhance success. They should be ready to cope withchanges as they occur. (Holcombe, 2008)Extreme Programming Life CycleThe traditional process of system development is linear with each lifecycle stage requiring theprevious stage to be completed. XP on the other hand, rather than using the linear fashion ofplanning, evaluating, and designing, it performs all the operations a little at a time throughout thephase of development. XP methodology resembles a jigsaw puzzle where many small pieces aredeveloped which may not make sense at individual level but upon combination result to acomplete package. The greatest advantage of this methodology is the resilience it offersenhancing easy change incorporation. (Lankhorst, 2012)XP process of system development begins with planning, and all iterations involves 4 basic lifecycle stages. These phases include; designing, testing, coding and listening. Planning- this is the first stage of extreme programming. In this phase clients meet with the teamdeveloper to create requirements. Team developer of Comfort Quilts Limited will change therequirements (a system that runs report for purchases and shipment methods) into iterations thattake a small portion of the feature or functionality needed. Combining iterations will offer theclient with the final product that is fully functional. Programmer team prepares the cost, plan andthe time needed to carry out the iterations and signing up of the iteration is done by individualdevelopers. One planning method is the crucial path approach. Iterations necessary for the
System Analysis 14 System Analysis Name Affiliate Institution_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
ICT310 System Analysis and Design - Assignment
|9
|1322
|149

System Analysis And Design Contents Contents
|11
|2087
|463

ICT310 : System Analysis and Design - Assignment
|10
|2093
|94

System Analysis and Design (SAAD) Assignment
|8
|1507
|160

System Analysis and Design | Report
|11
|1826
|72

System Development Methodology - Assignment
|10
|1554
|121