logo

The System Analysis and Design Assignment

   

Added on  2020-03-16

15 Pages1945 Words31 Views
Running head: THE SYSTEM ANALYSIS AND DESIGNThe System Analysis and DesignName of the StudentName of the University

THE SYSTEM ANALYSIS AND DESIGN1Table of ContentsPart A:..............................................................................................................................................2Scrum:..............................................................................................................................................2XP:...................................................................................................................................................3UP:...................................................................................................................................................5Part B:..............................................................................................................................................7Event table:......................................................................................................................................7Use Case:.........................................................................................................................................9Use Case Description:......................................................................................................................9Class Diagram:...............................................................................................................................10Domain Model Class Diagram:.....................................................................................................11Bibliography:.................................................................................................................................12Appendix:......................................................................................................................................14Memo:............................................................................................................................................14

THE SYSTEM ANALYSIS AND DESIGN2Part A:Scrum:Description: Scrum depends on using a cross-functional team. The team members ofscrum is self-organizing regarding the cause, which there is not another complete team leaderwho is able to decide the works of team members related to the project or takes initiation in theproblem solving among employees and project in-scope issues (Turk, France and Rumpe 2014).These reasons can be considered as the conditions, which are absolute through the teammembers, collectively, to be complete. Inside the agile Scrum approach, rather than providingcomplete, detailed descriptions of how all things are usually to become done on a task, the mostof it is left roughly the Scrum application implementation team. The reason why being the teamwill know best how to fix the trouble they can be presented (Abrahamsson et al. 2017). Advantages: The advantages are as following.1)Scrum makes sure that proper usage of capital and time is done2)The coding and testing is done during the sprint review phase 3)The project can be divided into small parts so that it can be achieved easily4)It allows the project manager to get feedback from the end users and customer5)If the project is fast moving then Scrum is perfect for the project (Fuggetta and DiNitto 2014)6)The daily scrum meetings are a great way of understanding the individual effortof each team members7)The short sprints are beneficial regarding entering new changes in the project

THE SYSTEM ANALYSIS AND DESIGN3Disadvantages: The disadvantages are as following1)The Scrum methodology is prone to scope creep issue, this happens because ofindefinite process description and unknown work flow2)If the project team is large in quantity, then Scrum can be a burden for projectmanager3)The project quality cannot be maintained throughout the project, only way out isaggressive testing process4)The team members can be irritated by daily team meetings (Abrahamsson et al.2017)5)The amount of negative impact falls upon the project on resign of a team memberis huge6)If the team members are not experienced then this framework is not suitableXP: Description: Extreme Programming (XP) can be referred to the software engineeringmethodology that is definitely the most noticeable an amount of agile software improvementpractices. Similar to the further agile procedures, Extreme Programming contrasts fromcustomary methodologies principally in engaging higher assessment on flexibility than onliability (Turk, France and Rumpe 2014). End users of XP concern continuing alterations torequirements just as one frequently usual and inevitable feature of software implementationprojects. It is to be assumed that adaptation to requirements alterations at any phase over theproject life is a convincing and enhanced method than inadequate to outline all requirements atthe beginning of a project and consuming strength to operate changes to the requirements.Software implementation activities within 1990s was formed by two chief influences such as

End of preview

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

Related Documents
Analyzing Extreme Programming (XP) Project Management
|4
|632
|50

The Advanced Information System Design
|3
|397
|38

System Analysis and Design Assignment Solution
|13
|3488
|158

Case of The System Analysis and Design
|17
|2719
|34

System Analysis and Design
|14
|1909
|73

Adaptive Methodologies for Odd Jobs Limited
|16
|3696
|367