System Analysis of CRM: Models and Use Case
Added on 2023-06-11
15 Pages2442 Words336 Views
Running head: SYSTEM ANALYSIS OF CRM
SYSTEM ANALYSIS OF CRM
Name of the Student
Name of the University
Author Note:
SYSTEM ANALYSIS OF CRM
Name of the Student
Name of the University
Author Note:
1SYSTEM ANALYSIS OF CRM
Table of Contents
Part A...............................................................................................................................................2
Task 1: Report..............................................................................................................................2
Task 2: Memo..............................................................................................................................5
Part B...............................................................................................................................................7
Task 3: Event Table.....................................................................................................................7
Task 4: Domain Class Model......................................................................................................8
Task 5: Class Diagram.................................................................................................................9
Task 6: Use Case Model............................................................................................................10
Task 7: Use case Description.....................................................................................................10
Bibliography..................................................................................................................................12
Table of Contents
Part A...............................................................................................................................................2
Task 1: Report..............................................................................................................................2
Task 2: Memo..............................................................................................................................5
Part B...............................................................................................................................................7
Task 3: Event Table.....................................................................................................................7
Task 4: Domain Class Model......................................................................................................8
Task 5: Class Diagram.................................................................................................................9
Task 6: Use Case Model............................................................................................................10
Task 7: Use case Description.....................................................................................................10
Bibliography..................................................................................................................................12
2SYSTEM ANALYSIS OF CRM
Part A
Task 1: Report
Spiral Model: This particular model is mainly considered to be perfect combination of
both iterative and waterfall model. It is inclusive of both controlled processing and systematic
progress of waterfall model in the iterative model (Sharma, Sabharwal and Sibal, 2014). This
particular process comes up with four kinds of phases. The four phases consist of stages like
identification, design, construction, evaluation and lastly proper analysis of risk. Identification
stage mainly initiate by proper collection of various requirements of business. The design mainly
deals with designing the various phase of the system. The design of software is mainly inclusive
of following things like logical, architectural and physical design. The actual software is mainly
developed in construct phase. Developed software is mainly created by taking into consideration
the requirements and design (Kazim, 2017). Analysis of risk is all about identification,
monitoring, analysis and estimation of various kinds of risk in the given project.
Benefits: There are large number of benefits of this model like:
Changing of requirement is mainly supported by this particular model.
Making use of prototypes is considered to be very positive thing about this model.
This particular model is considered to be useful in development of huge quantity
of prototypes.
Process or method of requirement analysis is mainly done accurately and very
finely.
Application of user can be easily seen in the earlier stage.
Drawbacks: There are several kinds of drawbacks of this Model like:
Part A
Task 1: Report
Spiral Model: This particular model is mainly considered to be perfect combination of
both iterative and waterfall model. It is inclusive of both controlled processing and systematic
progress of waterfall model in the iterative model (Sharma, Sabharwal and Sibal, 2014). This
particular process comes up with four kinds of phases. The four phases consist of stages like
identification, design, construction, evaluation and lastly proper analysis of risk. Identification
stage mainly initiate by proper collection of various requirements of business. The design mainly
deals with designing the various phase of the system. The design of software is mainly inclusive
of following things like logical, architectural and physical design. The actual software is mainly
developed in construct phase. Developed software is mainly created by taking into consideration
the requirements and design (Kazim, 2017). Analysis of risk is all about identification,
monitoring, analysis and estimation of various kinds of risk in the given project.
Benefits: There are large number of benefits of this model like:
Changing of requirement is mainly supported by this particular model.
Making use of prototypes is considered to be very positive thing about this model.
This particular model is considered to be useful in development of huge quantity
of prototypes.
Process or method of requirement analysis is mainly done accurately and very
finely.
Application of user can be easily seen in the earlier stage.
Drawbacks: There are several kinds of drawbacks of this Model like:
3SYSTEM ANALYSIS OF CRM
Managing of the given task is considered to be very complex in nature.
In some of the cases it can be easily encountered that project manager may fail to
understand the fact that the whole project has ended.
Number of spirals which are used in the project may fail to easily handle by the
project manager as the given quantity have increased over the period of time.
This particular model is not considering to be suitable for low risk kind of
projects.
Agile Model: It is considered to be as one of the popular model of SDLC as it allows
various project manager to handle projects in different ways. In agile Model, various kinds of
modification can be done about the current phase so this model can easily work with the given
requirement. Various kinds of activities in agile model are mainly put within the given time
frame so that this particular model can easily work at each and every stage of the given project
(Fuggetta and Di Nitto, 2014). Agile model comes up iterative approach which is used for
delivering application unit at each and every unit after the completion of given project at the end
of each and every iteration. Each unit of software is considered to be modified version of
previous model. The feedback of the various users comes up with great impact on the given
model. This model is considered to be adaptive in nature of SDLC in comparing to waterfall
model which is considered to be predictive in nature.
Benefits: Agile model comes up with large number of benefits like:
This model is considered to be very realistic kind of approach
This method mainly provides support for cross training along with team work.
Providing partial solution at beginning is considered to be crucial benefit
This particular kind of model does not require any kind of extensive planning
Managing of the given task is considered to be very complex in nature.
In some of the cases it can be easily encountered that project manager may fail to
understand the fact that the whole project has ended.
Number of spirals which are used in the project may fail to easily handle by the
project manager as the given quantity have increased over the period of time.
This particular model is not considering to be suitable for low risk kind of
projects.
Agile Model: It is considered to be as one of the popular model of SDLC as it allows
various project manager to handle projects in different ways. In agile Model, various kinds of
modification can be done about the current phase so this model can easily work with the given
requirement. Various kinds of activities in agile model are mainly put within the given time
frame so that this particular model can easily work at each and every stage of the given project
(Fuggetta and Di Nitto, 2014). Agile model comes up iterative approach which is used for
delivering application unit at each and every unit after the completion of given project at the end
of each and every iteration. Each unit of software is considered to be modified version of
previous model. The feedback of the various users comes up with great impact on the given
model. This model is considered to be adaptive in nature of SDLC in comparing to waterfall
model which is considered to be predictive in nature.
Benefits: Agile model comes up with large number of benefits like:
This model is considered to be very realistic kind of approach
This method mainly provides support for cross training along with team work.
Providing partial solution at beginning is considered to be crucial benefit
This particular kind of model does not require any kind of extensive planning
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
System Analysis of CRMlg...
|15
|2756
|331
Waterfall Model: Definition and Descriptionlg...
|7
|927
|304
SIT773 SOFTWARE REQUIREMENTS AND ANALYSIS.lg...
|5
|492
|58
Software Development Lifecyclelg...
|18
|3745
|95
System Analysis: Feasibility Study and Lifecycle Modelslg...
|24
|4376
|346
Software Engineering: Development Methods, Quality, Diagrams, and Lucid Chartlg...
|15
|4370
|101