Analysis Design Insights For IEEE Transactions On Wireless Communications

Benefits of Using Prototype Development Methodology

Software development can be defined as the proper type of the prototype model which helps in focusing on the factor that the given project is executed before the given deadline. This specific methodology primarily involves the various measures which easily gets involved in various developments which builds up the prototype for the given base. Then the client processes are started. The flow of the processes mainly involves the different types of the prototypes design and the client evaluation along with the reviews. management, it can be said that a proper prototype development helps in the deter development of the project.

• The Various kind of the risks that can take place in the given project can easily be identified.
• Error can easily be handled with proper review and evaluations.
• It becomes lot easier for the clients to understand the project using the prototype of the project.

• The number of the waste generated that reduces the number of the resources available for the project.
• It has been seen that the various request from the clients distracts the developer from the actual goal of the project.
• If the client asks for changes in the later stage of the development then it becomes difficult for the developer to go back.
• The various generated prototypes increases the amount of the development time and the price of the project.

This method is one of the best for the projects of short interval of times, and is one of the most efficient one. The strategy which makes that this process one of the available methodology is because of the factor that it ensures high quality of work in a very short interval of time. The developers also gets very much interested at the complexity of the projects are very much less and hence there are lots of scope to develop the best outcome.

Some of the major benefits of using this methodology is efficiency, time, client feedback and the risks in the methodology can be easily reduced. In cases of any error the amount of the changes that are to be made very less due to small size of the project. The profit amount in this process is very high due to small size of the projects. There are many kinds of benefits which can be obtained like feedback of client which helps in proper maintenance of standard. One of the major drawback of this methodology is the factor that it cannot be used for large projects which has many requirements.

Description: 

This development methodology is a part of agile methodology, which is mainly used of for the software development projects. The D.S.D.M. projects usually includes on RAD approach which mainly used for the different kinds of association provided by client side. The RAD approach is the business development of the project in a short interval of time. Apart from various objectives it also aims in giving programming models which is predefined in the given budget plan.  The different kind of involvements from the user’s side in the given process is generally prominent in nature. The expensive nature of this process from both the user and the developer side leads to very small profit from this procedure.

DSMD Methodology for Software Development Projects

Description: 

The joint application development methodology primarily focusses on the involvement of various users at a given interval of time for a given project. These workshops are commonly known to be the JAD sessions. It has more customer loyalty due to the factor that it is rated according to the client for given phase of the project. This methodology is primarily developed for the various kind of the frameworks related to the PCs. There are various kind of the users and the developers are connected in the same time and hence there are more scopes of discussion. The stakeholder expectation are much higher in this methodology. There are many of the drawbacks in this methodology and is also a very inefficient way of development.

For proper kind of methodology, it should be taken into account neglected organization is considered to be small one. It is suggested to implement waterfall model as it will help them in increasing the size. On the contrary for large size organization it is generally suggested that they should implement to make use of RAD technology to their given software development. This particular method or process is considered to be efficient and various kinds of development cost of the given cost of project is mainly considered to be easily bearable by the given organization taking account of the size of the given organization.

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

There is various type of difficulties which are faced by the organization in the present time. This has brought about the need for the development of a user centered Design. Hence there is a proposal to develop a solution which is user centric and the developed system would be able to produce an efficient solution that would be perform functions that would be helping the organization in reducing the response time.

The system would bring about efficient solution and make the procedures of the organization automated. The system would also reduce the time required for management of the workload and increase the efficiency of the organization. The major procedures of the organizations are also handled by the system.

Event	Event Type	Trigger	Source	Activity/Use Case	System Response/Output
ABN Record	Internal	The system has enter the ABN number of the customer id	Sales Representative	ABN details Record	Customer details are stored
Filling of application form	External	Entry of customer details	Customer	Application Form	Accepting the submission of form
Application Review	Internal	the form being reviewed by the admin	Management	Application Review	Analyzing the provided application
Customer Details Record	Internal	Entry of customer details into the system	Sales Representative	Customer Details Record	Customers Details are stored
Select order	External	Customer make selection  of order	Customer	Selection of Order	Customer select the items
Online Orders placing	External	Place the orders selected	Customer	Product Order Online	Items Placed into the Customer’s account
Review Order before Placing	External	Customer reviews the order		Customer Review order	Producing the items details to the customers
Order Confirmation	Internal	Selecting the order to confirm	System	Confirm Order	Customer order is stored in the system
Review Order after Placing	Internal	Customer placed orders are reviewed	Management	Management  Review order	Producing the items details to the management
Check Order Progress	Internal	tacking the progress of the order	Customer	Track Orders	Order Progress being displayed by the system
Order Delivery	Internal	Delivery of the product	Delivery Staff	Deliver Order	System stored the delivery order
Maintain the record	External	Maintaining the record of the report	Management	Maintain the Record	System stored the record
Identify Customer	Internal	Viewing the actions of the customer	Management	Identify Customer	Stored the visit of the customers in the system
Track visits of Customer	Internal	tracking of customers’ orders online	Management	Track Customer Visits	Displayed the customer’s order details
Check Sales Report Monthly	Internal	Generating of monthly sales report	System	Monthly Report of Sales are Checked	Displayed monthly sales report
Running the sales report	Internal	Analyzed the sales report	Management	Displayed the sales report analyzed	Displayed the analysis of sales report

Use Case Name:	Application review
Scenario	The application would be reviewed by the management
Triggering Event:	The application would be submitted by the customer.
Brief Description:	The application is reviewed and it is decided if the application is accepted or not.
Actors:	The management, the customers
Related Use Case:	Not applicable
Stakeholders:	The customers
Precondition:	The details of the customer are entered in the application.
Post Condition:	The customer would be registered in the system.
Flow of Activities:	Actor	System
1. The customer would enter the application 2. The application of the customer is accepted/rejected.	1. Send for review 2. Rejected or accepted
Exception Conditions:	The ABN of the customer is absent.

 

References

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: Accounting.

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.