Advantages of Development Methodologies

In the UP development methodology the project is developed with the least cost and within a least amount of time. In addition to this, the development is very fast and organization is able to deliver the project within a very short span of time. The main idea behind this type of development for an organization is that the development should be done in time and money that is one third of the actual requirement for the organization. The additional procedures that are involved with the development of a project are generally, excluded from this project.

Advantages: The main advantages of the methodology are:

• The methodology takes less time than the other methodologies. The cost of development is also reduced for this type of methodology.
• The methodology builds up collaborations and team work within the project team.
• The errors are also reduced for the project.

Disadvantages: The main disadvantages of the methodology are:

• The success depends entirely on the support and the co-operation of the team members within the project.
• This methodology is unable to offer any kind of flexibility to the members of the project or the developer for the project for that instant.

Methodology 2: XP Methodology

Description: 

The XP methodology the development of the project is very flexible and the method is very beneficial for projects that are very complex and this methodology is usually adopted by large businesses. The method involves four stages that are Designing, Listening, Coding and Testing. The four method procedures are incorporated within the development of the project by the organization.  

Advantages: The main advantages of the methodology are:

• The methodology helps in reducing the budget of the development of the project.
• The methodology also helps in the development of the communication link in between the customers and the organization.
• The practical planning and scheduling process is very efficient in this methodology.

Disadvantages: The main disadvantages of the methodology are:

• The requirements change in this methodology and hence the development cost of the project increases with each and every change in the requirement.
• The success of the project depends entirely on the individuals involved in the project and also the performance of the people involved in the project.

Methodology 3: SRUM Methodology

Description:

The SRUM methodology is very important for the development of the innovative and complex procedures. Hence, the methodology is applied in large scales, however the project methodology has its disadvantages as well. In this methodology the project owner creates a backlog for the system and the team also conducts a planning system where the project processes are broken into smaller blocks and these blocks are executed one after another. Brief meetings are held regularly and the result to the meetings are carried forward to the next meeting.

Advantages: The main advantages of the methodology are:

• Time and money is used effectively in this methodology.
• Dividing the larger projects in to smaller blocks makes it easy for the developer to execute the project.
• The project team get a clear idea about what is to be implemented in the project for the organization.

Disadvantages: The main disadvantages of the methodology are:

• The scrum methodology often leads the project to a scope creep and this hampers the schedule of the project.
• The project quality is very for the SCRUM framework to maintain. In addition to this, the adopting the framework for a large team is very difficult in this methodology.

Methodology 4: RAD development methodology  

Description:

RAD is the Rapid Application Development procedure and hence, rapid development of application takes place in this methodology. The methodology involves very minimum planning that is to be used for the development of the project. The methodology involves procedures such as including requirement testing and capturing.

Advantages: The main advantages of the methodology are:

• The Rapid Application development is used for the increased speed of development and the quality of the project.
• The development methodology also provides a great visualization for the clients in the system.

Disadvantages: The main disadvantages of the methodology are:

• The Scalability of the software application is very less in this type of application
• In addition to this, the software produces reduced features for the software as the process starts as a prototype and ends as a finished application.

For recommendation it can be said that the RAD development sis very important development and can be used as the development tool of the small and medium sized business organizations. Hence, this methodology can be referred as the suitable method. In addition to this, the large scale organizations can adopt the method of extreme programming and use it to their benefit.

Re: Adopting a User Centered Design (UCD) approach and setting a plan for the development of the Human Computer Interaction (HCI)

The association is as of now confronting challenges in utilizing the manual methods for getting the data in the framework. There has been a requirement for the advancement of a human cooperation that would help the association in different ways. It is being suggest that the data framework is made client driven and the improvement of the framework ought to likewise help in progression in the systems and diminishing the reaction time for the association.

The arrangement would make the strategies of the associations computerized and this would assist the association with achieving an awesome level of effectiveness and make the business methodology of the association compelling. Furthermore, the framework would be extremely useful in playing out the undertaking of decreasing the workload of the association and this would likewise help the association in keeping up the business techniques productively. What’s more, the framework encourages the association to keep up the critical techniques and perform them proficiently.

Event	Event Type	Trigger	Source	Activity/Use Case	System Response/Output	Destination
Fill in customer Application form	External Event	The application form is submitted	Sales Representative	Application	Sending application for review	System
Reviewing of the customer application  form	External Event	The application form is stored in the system.	System	Review Application	The system requests the confirmation from the management	Management
Storing the details of the application	Internal Event	The details of the application are uploaded in the system.	System	Store Customer Details	The details of the application is stored in the system.	Sales Staff
The business number of the applicant is recorded	Internal Event	The customers enters the ABN number	Sales representative	Store ABN	Stores the ABN	System
Run the monthly sales report	Internal Event	The monthly sales reported is generated.	System	Monthly sales Report	Displays the monthly sales report	Management
Display the amount of sales	External Event	Running the monthly sales report is completed	System	Display amount	List of sales amount	Management
Display the per area sales	External Event	Running the monthly sales report is completed	System	Display sales	List of sales amount	Management
Display per sales person	External Event	Running the monthly sales report is completed	System	Display sales person	List of sales amount	Management
Record of the sales visit	Internal  Event	The customer has completed visiting the site.	System	Recording sales visit	The sales visit are stored in the system.	Management
Identify unsuccessful visit	External Event	The customer visit is unsuccessful	System	Identifying unsuccessful visits	The visits are analyzed by the system	Management
Identify as potential customers	External Event	The potential customer is indicated.	System	Potential customers	Displays the list of potential customers	Management

Use Case Name:	Record customer Details
Scenario:	The system would record the details of the customer
Triggering Event:	The sales person would be entering their details
Brief Description:	The ABN number of customer is recorded in the system
Actors:	The sales representative
Related Use Case:	Not applicable
Stakeholders:	The customers
Precondition:	The details of the customers are to be stored in the system.
Post Condition:	The customer would be registered in the system.
Flow of Activities:	Actor	System
1. Enter customer details	1. Store details
Exception Conditions:	The registration of the customers are not valid.

Alkhateeb, A., Nam, Y.H., Rahman, M.S., Zhang, J. and Heath, R.W., 2017. Initial beam association in millimeter wave cellular systems: Analysis and design insights. IEEE Transactions on Wireless Communications, 16(5), pp.2807-2821.

Azar, A.T. and Vaidyanathan, S. eds., 2015. Chaos modeling and control systems design (Vol. 581). Germany: Springer.

Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-oriented approach with UML. John wiley & sons.

Dong, X., Shi, Z., Lu, G. and Zhong, Y., 2015. Formation?containment analysis and design for high?order linear time?invariant swarm systems. International Journal of Robust and Nonlinear Control, 25(17), pp.3439-3456.

McCuen, R.H., 2016. Hydrologic analysis and design (Vol. 3). Prentice Hall.

Montgomery, D.C., 2017. Design and analysis of experiments. John wiley & sons.

Rashid, M.H. ed., 2017. Power electronics handbook. Butterworth-Heinemann.