Securing Higher Grades Costing Your Pocket? Book Your Coursework Help at The Lowest Price Now!

  • +1-617-874-1011 (US)
  • +44-117-230-1145 (UK)
Online Customer Service

ICT700 System Analysis and Design Management

Discuss about the:-

Part A

A JAD session with key stakeholders revealed the following information. The business processes described below are the system requirements for this information system solution:

It has been decided to focus of building and implementing the customer relationship management application and run a separate project for the purchasing project later.  Therefore, do not model any of the purchasing system (this is where FFSL purchase from their suppliers).
Before a retail store can become a customer of FFSL, that store must fill in an application. Applications are reviewed by the management team and not all applications are approved. FFSL records the following details for all customers: Name, Business number, Address, Telephone, Email, Application date, Discount level, Sales area, and Date last visited.

Part B

The geographical sales areas for the sales people have been defined for the whole of Australia using current population numbers, however FFSL does not yet have enough sales people to cover all of Australia so some sales areas do not yet have a sales person assigned while some sales people are assigned to more than one geographical sales area in cities such as Melbourne.
Steven Smith wants to run a sales report on the first of every month that shows the amount of sales, per sales area and per sales person.
Steven Smith also requires that the following information on each sales visit be kept, the customer, the date of the visit, sales people (s) who visited, and amount of order.  Please note for unsuccessful sales visits to potential customers, it is planned that a customer called "potential customer" be created for each geographical sales area to track these visits.
The party plan representatives are expected to manage their own customers and work load so FFSL so does not store any details of the parties held.  


Part A:


Description: Scrum depends on using a cross-functional team. The team members of scrum is self-organizing regarding the cause, which there is not another complete team leader who is able to decide the works of team members related to the project or takes initiation in the problem 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 team members, collectively, to be complete. Inside the agile Scrum approach, rather than providing complete, detailed descriptions of how all things are usually to become done on a task, the most of it is left roughly the Scrum application implementation team. The reason why being the team will know best how to fix the trouble they can be presented (Abrahamsson et al. 2017).

Advantages: The advantages are as following.

  • Scrum makes sure that proper usage of capital and time is done
  • The coding and test

    ing is done during the sprint review phase
  • The project can be divided into small parts so that it can be achieved easily
  • It allows the project manager to get feedback from the end users and customer
  • If the project is fast moving then Scrum is perfect for the project (Fuggetta and Di Nitto 2014)
  • The daily scrum meetings are a great way of understanding the individual effort of each team members
  • The short sprints are beneficial regarding entering new changes in the project

Disadvantages: The disadvantages are as following

  • The Scrum methodology is prone to scope creep issue, this happens because of indefinite process description and unknown work flow
  • If the project team is large in quantity, then Scrum can be a burden for project manager
  • The project quality cannot be maintained throughout the project, only way out is aggressive testing process
  • The team members can be  irritated by daily team meetings (Abrahamsson et al. 2017)
  • The amount of negative impact falls upon the project on resign of a team member is huge
  • If the team members are not experienced then this framework is not suitable


Description: Extreme Programming (XP) can be referred to the software engineering methodology that is definitely the most noticeable an amount of agile software improvement practices. Similar to the further agile procedures, Extreme Programming contrasts from customary methodologies principally in engaging higher assessment on flexibility than on liability (Turk, France and Rumpe 2014). End users of XP concern continuing alterations to requirements just as one frequently usual and inevitable feature of software implementation projects. It is to be assumed that adaptation to requirements alterations at any phase over the project life is a convincing and enhanced method than inadequate to outline all requirements at the 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 internally, object-oriented programming substituted procedural programming as the programming pattern utilized (Krahn, Rumpe and Volkel 2014).

Advantages: The advantages are as following.

  • The software development team can have required time and capital so that project can be realized property, the time and cost saving feature of the mythology allows it
  • The main focus of the methodology remains on the delivery of final product on time and this save a lot of time for team
  • The use of less documentation is the reason behind cost saving (Estler et al. 2014)
  • The discussions among the members is the way of solving the problems
  • The methodology is very simple

Disadvantages: The disadvantages are as following.

  • Putting more focus on codes rather than design of the system can be harmful thing
  • The low quality of design often becomes a drawback (Krahn, Rumpe and Volkel 2014)
  • The software can be of low quality


Description: The Unified Process (UP), or simply Unified Software Development Course of action, is a iterative and also incremental software development platform from which a customized activity is usually defined.  This platform is made up of many elements and features really been transformed numerous moments in making quite a few variations.  The most well-liked distinctions range from the Realistic Unified Course of action (RUP) as well as Clear Unified Course of action (OpenUP) (Fuggetta and Di Nitto 2014).  This platform carries quite a few important features what apparently bring on pretty much all variations. It is really an iterative and also incremental improvement framework. It can be architecture-centric with huge function being carried out to make sure you identify and also validate a system design and style for all cryptography is without a doubt done. It can be risk-focused and also draws attention that highest-risk reasons wind up being answered found in the earliest deliverables possible (Kaur and Sengupta 2013). It can be use-case and also UML style enticed with most conditions staying known found in one of those forms.

The phases of the methodology are as following.

Inception: The primary target about the Inception phase may be to grow the truth for the viability from the planned system. This four fashions tend to be discussed this huge a natural part of it sequence, This All five Workflows (Perkusich et al. 2015). The major milestone regarding the Inception phase is named Life-Cycle Objectives.

Elaboration: The primary target about the Elaboration phase may be to grow the cabability to put together the new process offered these money restrictions, routine restrictions, or other varieties restrictions that the increase undertaking faces (Fuggetta and Di Nitto 2014). This initiates if this part tend to be catching a normal functioning flavor the remaining functional conditions, growing these pick construction right into a entire system basic, which happens to be a inner relieve the system guided toward meals these construction, spanning critical hazards during an on-going time frame and also finalizing the corporation case for the undertaking and also making some sort of undertaking program which contains enough details to steer the next phase from the project.

Construction: The primary target about the Construction phase is without a doubt to construct a head unit proficient at running productively found in toy with customer’s environments (Perkusich et al. 2015). During Construction, these undertaking club works tasks that involve generating the system iteratively and also incrementally, ensuring that these viability from the process is consistently proven found in practicable form.

Transition: The primary target about the Transition phase may be to list out fully functional process to make sure you customers. During Transition, these undertaking club is targeted on fixing issues and also modifying the system to mend earlier unidentified problems. The major milestone regarding the Transition phase is named Device Release.

Part B:

Event table:


Event Type



Activity/Use Case

System Response/



Purchase from supplier


Product stock of FFSL is to be in creased

Management and Warehouse


Update Stock, Product Availability


Filling application


The management will review and register retail store

FFSL Potential Customer

Creates Customer

Update Customer base, read application data, verification

Retail store

Tracking Sales Person Area


The areas of sales personnel will be divided and activity of individuals monitored

Sales Personnel of FFSL

Input Sales Details, Sales Area Coverage

Read sales personnel related data,

Update area

Sales Person

Sales Tracking


Creating report on sales

Steven Smith

Sales Report

Create report based on sales data

Sales Person

Visit Data View


Generating information based on sales person visit to customer

Steven Smith

Visit Customer, Failed Visit, Make Order

Create a list of visited customer along with date and sales person who visited him and amount of order made

Sales Person

Use Case:

Use Case Description:


Creates Customer



Brief Description

The retail stores will fill the form and register to be the customer of FFSL


Customer table will be updated with a new entry


All the filled data must be authentic and valid in the application form

Post Condition

The retail stores must pass the criteria to be a customer


Retail Store


Fill the application form

Collect data from form


Analyze data

Provide additional details to management if required

Analyze those data


Accepts the application


Registers as customer


Retail store not in the area but has all the eligible features

Class Diagram:

Domain Model Class Diagram:


Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.

Estler, H.C., Nordio, M., Furia, C.A., Meyer, B. and Schneider, J., 2014. Agile vs. structured distributed software development: A case study. Empirical Software Engineering, 19(5), pp.1197-1224.

Fuggetta, A. and Di Nitto, E., 2014. Software process. In Proceedings of the on Future of Software Engineering (pp. 1-12). ACM.

Kaur, R. and Sengupta, J., 2013. Software process models and on failure of software development projects. arXiv preprint arXiv:1306.1068.

Krahn, H., Rumpe, B. and Volkel, S., 2014. Roles in software development using domain specific modeling languages. arXiv preprint arXiv:1409.6618.

Perkusich, M., Soares, G., Almeida, H. and Perkusich, A., 2015. A procedure to detect problems of processes in software development projects using Bayesian networks. Expert Systems with Applications, 42(1), pp.437-450.

Sharma, C., Sabharwal, S. and Sibal, R., 2014. Applying genetic algorithm for prioritization of test case scenarios derived from UML diagrams. arXiv preprint arXiv:1410.4838.

Störrle, H., 2014. On the impact of layout quality to understanding UML diagrams: size matters. In International Conference on Model Driven Engineering Languages and Systems (pp. 518-534). Springer, Cham.

Storrle, H., 2016. On the impact of size to the understanding of UML diagrams. Software & Systems Modeling, pp.1-20.

Turk, D., France, R. and Rumpe, B., 2014. Assumptions underlying agile software development processes. arXiv preprint arXiv:1409.6610.

Turk, D., France, R. and Rumpe, B., 2014. Limitations of agile software processes. arXiv preprint arXiv:1409.6600.

This problem has been solved.

Please send an Email to with the Payment ID and the link to the document to collect by email

Cite This work.

To export a reference to this article please select a referencing stye below.

Urgent Homework (2022) . Retrive from

"." Urgent Homework ,2022,

Urgent Homework (2022) . Available from:

[Accessed 04/10/2022].

Urgent Homework . ''(Urgent Homework ,2022) accessed 04/10/2022.

Buy ICT700 System Analysis and Design Management Answers Online

Talk to our expert to get the help with ICT700 System Analysis and Design Management Answers to complete your assessment on time and boost your grades now

The main aim/motive of the management assignment help services is to get connect with a greater number of students, and effectively help, and support them in getting completing their assignments the students also get find this a wonderful opportunity where they could effectively learn more about their topics, as the experts also have the best team members with them in which all the members effectively support each other to get complete their diploma assignments. They complete the assessments of the students in an appropriate manner and deliver them back to the students before the due date of the assignment so that the students could timely submit this, and can score higher marks. The experts of the assignment help services at are so much skilled, capable, talented, and experienced in their field of programming homework help writing assignments, so, for this, they can effectively write the best economics assignment help services.

Get Online Support for ICT700 System Analysis and Design Management Assignment Help Online


    • 24 x 7 Availability.
    • Trained and Certified Experts.
    • Deadline Guaranteed.
    • Plagiarism Free.
    • Privacy Guaranteed.
    • Free download.
    • Online help for all project.
    • Homework Help Services

Tap to Chat
Get Instant Assignment Help
Tap to Chat
Get Instant Assignment Help