Essay: Prioritizing Requirements In Software Development Life Cycle.

An approach for integrating the prioritization of functional and nonfunctional requirements.

Analysis of software security model in scenario of Software Development Life Cycle (SDLC).

Suitability of Existing Software Development Life Cycle (SDLC) in Context of Mobile Application Development Life Cycle (MADLC).

Collaboration Methodology for Integrating Non-Functional Requirements in Architecture.

Analysis of Software Security Model in SDLC

1. Message Displaying: This particular system will display different messages as well as responses to customers throughout the display that is installed in pillars. Once user appears at pillar, the sensor installed in particular system senses the presence of vehicles and display the required messages as well as options.
2. Authentication:This is the process to verify a user by doing real time checking of ticket and retrieving all types of details from their saved databases. Once the ticket validation is done, customer will get authenticated to enter the parking lot.
3. Authorization:This the process to authorize the validation of the user request for the parking area. The whole process is consists of different levels that also different for both fixed customers and normal customers. The whole authorization process gets done from the core of any system. The identification of customers will be done by doing the proper uses of issues ticket.
4. Handing of Payment:This particular system will also check the payment done. For some fixed customers, the system takes all charges for ticket at a time of generation. The card will be entered to ticket reader device and the exact payment gets deducted by calculating the parked time. The payment of parking card can also be done by using debit/credit card or cash.
5. Report Generation:The system will generate reports retrieving their stored data and information. This report can only be accessed by the management supervisors only. It also generates report in all weekly basis, monthly as well as on yearly basis also. The report get stored in the system for life time so that it can be checked any time.
6. Storage of Data:This particular system gets inputs from all customers and stored their inputted data on the system database. The storage of data will be done after doing different levels of authentication as well as validations.

1. Availability:This automated system is available for 24*7 to provide services. The customer can park their vehicles at any time of the day. To maintain the space availability, there will be an appointed person who will look after any space related issues and functioning of system.
2. Recoverability:The system will also be outfitted with an effective disaster recovery technique. In case of any data theft and data loss, the organization has the back-up plan to collect data with the help of implemented data recovery technique.
3. Security:In today’s modernized world, securing the ICT system is one of the major concerns. The system will not get accessed on any peripheral devices, because it can be any other types of direct injection of any infected viruses. The system gets secured with three layers of approaches which do not allows any un-authorized users to access the database system.
4. Scalability:With the scalability process, it mainly discusses about the capabilities of system to get accompanied with the business requirements. It also discussed about the system which will use the resource based on the speed of car appearing. In terms of gaining the profit, the system also generates different forecasting reports that allow management to do identification of resource required. With the help of appropriate scalability, the system gets ready to provide better services to the customers.
5. Usability:The use of the installed system will be on its high quality. The customer will perform all pre-determined tasks based on the instructions that appear of the display.
6. Use Case Modeling:

Figure 1: the Use Case Diagram of Collin’s Parking Car Park System

(Source: Created by Author)

Use case 1- reservation

The fixed customer can get the accessibility to reserve their parking area by doing the proper authentication and inputting all types of details like time and date, vehicles number, reservation number, duration of stay, parking slot number etc. The confirmation of all these information gets him the accessibility to create reservation in the parking area database.

Use case 2 – Car Parking

As soon as any user move towards the entry gate the installed camera reads the license plate and do searing in database to does the authorization of customer level fixed or normal. Them accordingly, the booked space will get displayed on the screen or if the user has not done any prior booking then the parking spot will get allocated to them based on availability. In case if the system will not be able recognize the license number with stored database, user need to manually input their all details like registration number and any other details.

Use case 3 – Account Supervision

The existing space allocated to any fixed users can be changed by doing proper authentication based on their availability. Therefore, the edit option is used as sub case.

Use Case 4 –Registration

This will be used by the unregistered users to register them with the car parking system. If the user is the first visitor then they need to enter all their required details and submit it to the installed system. However, if the user is a repeated visitor then they need to put some details whereas other details will be there which was auto-saved from the first time entry.

Use case 5 – View Registration

In this after doing the registration with the system, both the user and supervisor can check the details and also get it validated.

Use case 6 – Parking Space Management:

In this, the usage history, parking price rate, balance availability on wallet will be checked with the installed application and also be viewed by the users also.

Use case 7–Edit reservation

To do any types of edit in the provided details or to delete/entry the registration, users need to provide input before a certain time so that all details can be processed in accurate manner.

Use case 8–registeration of vehicle

In this, the user needs to put all details like insurance, license number etc to the system which will record all details and register the vehicle to this parking system.

Suitability of Existing SDLC in MADLC

Use case 9–Edit vehicle details

If needed the user can also get the accessibility to edit all details entered at the time of registration

Use case 10–Authenticate user

The account for any fixed user is only created in the system, the user just need to login to the system. All details are get automatically fetched from the stored database which users can automatically access the stored details.

Use case 11–Set price

Different tariff plans will be shown to the users and the user can choose their plan based on their needs.

Use case 12–inspect usage history

This can only be accessed by the system supervisors to view all details of users and also can checked the usage history of all types of users both fixed and ordinary.

Use case 13–Monthly billing

If in case the user opt for post-paid option, the machine generated bill get operated on monthly basis and sent to their registered emails and phone numbers so that it can be paid on time.

3.   UML Domain Model Class Diagram

Figure 2: the Domain Model Class Diagram of Collin’s Parking Car Park System

(Source: Created by Author)

From the above class diagram, the representation of Collin’s Car Parking system is done properly. The classes are mainly designed to achieve more business operations. Since, the system will be only interacting with the customers only. The customer will be considered as an external entity. The class has two types of operations like creation and deletion of any customer. For the fixed customer, details will be stored in the database, and for the ordinary customer new class will get designed. All ticket class has different relevant information and also have unique id. For the fixed user ticket, the duration of stay will be presented and the permanent type of ticket will display the payment done type whether it is post-paid or pre-paid.

SDLC (Software Development Life Cycle) is a process used by any industry to have the proper designing and maintaining the software quality. There are five different stages of SDLC like planning stage, Designing stage, Building Stage, testing and implementation stage.

Planning Stage: In this stage, it discuss about different needed equipments for Collin car park system are analyzed. All this analysis process will be done by the supervisor’s management of Collin Parking system. It also discussed about the quality assurance of requirements as well as various faced risks of this system. A proper planning is done for the designing of entire parking system.

Collaboration Methodology for Integrating Non-functional Requirements in Architecture

Designing Stage: In this stage, it discussed about all things that mainly required for the Collin’s Parking System. The PCB board that required designing the parking system is installed in this phase. All the stakeholder of this parking system will do the proper analysis based on risk analysis, mitigation process, and required budget of the newly designed system.

Building Stage: In this phase, it mainly discuss about the actual development of the system. The design of car parking system is discussed in detailed manner and all the codes are generated to have the proper design of parking system. Proper coding will be done with the help of different language for the better car parking system.

Testing Stage: it is one the important stage of SDLC where the testing of newly designed system will be done. In this stage, the design of parking system will be tested by implementing as dummy way whether it is performing properly or not.

Implementation Stage: After the testing phase, it comes of the deployment as a final stage in real time. However, after that, it also be modified based on the feedback of users. The maintenance ways of this parking system is also discussed in this stage.

References

Alshamrani, A., &Bahattab, A. (2015). A comparison between three SDLC models waterfall model, spiral model, and Incremental/Iterative model. International Journal of Computer Science Issues (IJCSI), 12(1), 106.

Dabbagh, M., & Lee, S. P. (2014). An approach for integrating the prioritization of functional and nonfunctional requirements. The Scientific World Journal, 2014.

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

John, S. K., &Swapna, K. (2017). A New SDLC Frame Work for Website Development. AADYA-Journal of Management and Technology (JMT), 7, 132-142.

Karim, N. S. A., Saba, T., &Albuolayan, A. (2017). Analysis of software security model in scenario of Software Development Life Cycle (SDLC). Journal of Engineering Technology (ISSN: 0747-9964), 6(2), 304-316.

Kaur, A., & Kaur, K. (2015). Suitability of Existing Software Development Life Cycle (SDLC) in Context of Mobile Application Development Life Cycle (MADLC). International Journal of Computer Applications, 116(19).

Khan, F., Jan, S. R., Tahir, M., Khan, S., &Ullah, F. (2016). Survey: Dealing Non-Functional Requirements at Architecture Level. VFAST Transactions on Software Engineering, 9(2), 7-13.

Khan, P. M., & Beg, M. M. (2014). Measuring Cost of Quality (CoQ) on SDLC Projects is indispensible for effective software quality assurance. arXiv preprint arXiv:1405.4824.

Khan, S., Babar, M., Khan, F., Arif, F., & Tahir, M. (2016). Collaboration Methodology for Integrating Non-Functional Requirements in Architecture. the Journal of Applied Environmental and Biological Sciences (JAEBS), 6, 63-67.

Pandey, A., & Banerjee, S. (2015). Search based software testing: An emerging approach for automating the software testing phase of SDLC. Proc. ICRCWIP.

Rahman, M., & Ripon, S. (2014). Elicitation and modeling non-functional requirements-A pos case study. arXiv preprint arXiv:1403.1936.

Rhazali, Y., Hadi, Y., &Mouloudi, A. (2014). Transformation method CIM to PIM: from business processes models defined in BPMN to use case and class models defined in UML. International Journal of Computer, Electrical, Automation, Control and Information Engineering, 8(8), 1453-1457.

Shah, S. A. A., Shahzad, R. K., Bukhari, S. S. A., &Humayun, M. (2016). Automated Test Case Generation Using UML Class & Sequence Diagram. British Journal of Applied Science & Technology, 15(3).

Yue, T., Briand, L. C., &Labiche, Y. (2015). aToucan: an automated framework to derive UML analysis models from use case models. ACM Transactions on Software Engineering and Methodology (TOSEM), 24(3), 13.