6-8 pages, APA format.  Reference documents attached.

The design phase of the software development process is complete and implementation is under way. It is during this phase that quality becomes an issue and the verification and validation process must be employed. The most important aspect of Quality Assurance is planning. Verification and validation processes rely heavily on the requirements for a software application, and a good test plan should be based on the requirements to ensure they are met. For this assignment, you will be preparing a test plan for your application and adding this test plan to your Software Development Plan that you have been working on in the first three modules of the course

The project deliverables are:

• Title Page
• Table of Contents
• Test Plan
  • Write a section of your report to address the quality standards and goals to be achieved by the verification and validation process. The standards should define the level of quality required before the application is released into production and should be stated in measurable terms.
  • Prepare a test coverage matrix based on the requirements of your application you wrote previously. The test matrix should demonstrate that your tests will provide full coverage of the application.
  • Write a white box test plan to be used during the implementation phase of the project. The white box test plan should address some parts of the test matrix and should provide guidance to ensure the quality of the code meets the internal quality standards defined for the project. Test cases should accompany the white box test plan.
  • Write a black box test plan to be used for completed application modules and for functional testing after the application is functionally complete. The black box test plan should address parts of the test matrix and should include test cases.
  • Execute your test plans and provide results of your tests.

Trident University International
Richard D. Pelrine II
Module 2 Case Study
CSC424 Software Engineering (JAN2017FT-1)
Dr. Brian Holbert
January 29, 2017 CSC424(JAN2017FT-1) - Module 1 Session Long Project Table of Contents
1.
2.
3.
4.
5.
6. Project Summary
Functionality
Budget of software
Time frame
Software Development Methodology
Roles and Responsibilities 3
3
3
3
4
4 CSC424(JAN2017FT-1) - Module 1 Session Long Project
Project Summary
roomMaster is a property management software created by InnQuest. This software is
helpful in managing property for hotels and resorts. It allows companies to handle overall
management of a hotel including allowing customers to book rooms directly using a web-based
interface on a supported vendor’s site. In addition, customer information and queries are saved
into a single database for later reference. You can view the number of available rooms in your
hotels and information about customers who are staying in your hotel (InnQuest Software, 1994).
The software development plan will provide step-by-step information about the
development of a project for this particular software. Sections to be included in the software
project development plan are: time requirement, budget limitations, development team size,
their roles and responsibilities, the desired outcome of the project, the customer base, the
possibility of breakdowns, etc. The roomMaster software manages booking of hotels.
Functionality
Customers can make reservations for rooms using booking engines such as Expedia.com,
Booking.com, etc. These booking engines interact directly with roomMaster’s interface to
provide customer information including billing, and contact methods. As an administrator, you
can access and design security for your database. Accounting, reporting, integrating, automatic
check-in, check-out are other services provided by roomMaster software.
Budget of software
Various factors on which budget of a software depend are size of software, functionality
provided by software, scope of software, design of software, number of people working on
development process of software. CSC424(JAN2017FT-1) - Module 1 Session Long Project Time frame
Time frame of a software depends on its functionalities, usually it takes 4-6 weeks for a
small piece of software. It also depends on the skills of development team. For example: if
highly skilled personnel are working on this software, it takes less time to complete. The size of
developing team also affects the time required to complete SDLC. Software Development Methodology
Software development methodology provides a framework of techniques used to develop
software. For the roomMaster software, we will use the dynamic systems development method.
This approach adapts to the quick application advancement philosophy. It is a repetitive and
step-by-step approach that focuses on the requirements of the customer. This approach plans the
software advancement design according to predefined time period and the assigned spending
plan. This is the reason why it is very popular in the realm of software development, nowadays.
The benefits of using dynamic systems development approach for software development is that
customers are continuously contacted for feedback with the intent of using it for product
advancement. Performance is good and offers simple access to end clients by the designers. In
roomMaster software, the client interaction is very important as customers make online
reservations for rooms and as stated earlier, dynamic software development approach provides
interaction with clients, so it is the best approach for developing roomMaster software (Rangel,
2016). CSC424(JAN2017FT-1) - Module 1 Session Long Project
Roles and Responsibilities: There are many people involved in a software development plan: Project manager
System analyst
Designer
Programmer
Tester Projector manager: Success of a project depend on how efficiently is the project
development is planned and how the development team is working together. The project manager
is responsible for planning a project, assign activities to development team, provide resources
and interact with client to gather the details of project.
System analyst: System analysts study the requirements provided by customer. They
check whether or not these requirements are feasible.
Designer: The system designer designs the architecture of the software. Various tools
such as UML, ER diagrams, logical diagrams are used by the designer to design the software.
Programmer: The programmer implements the designs made by designer. Various
languages like C, C++, java, PHP and many more are used to implement the software.
Tester: After successful implementation of software, it is verified by tester. Tester test all
the possible breakdowns of a software. If they are tolerable then it is further passed to customer
otherwise it is send back to programmer for further improvements. CSC424(JAN2017FT-1) - Module 1 Session Long Project
References:

 

Running head: ROOMMASTER 1 Room Master
Student Name
Course Name
February 17, 2017 ROOMMASTER 2
Software Requirements Specifications This Software Requirement Specification archive gives a total portrayal of the considerable
number of functionalities and the details of the RoomMaster software. The engineers and the
analyzers can utilize this archive as a source of perspective for building up the outline and test
arrange reports. The aim behind this assignment is to exhibit a point by point RoomMaster
software. It will clarify the distinctive utilitarian and also non-useful prerequisites of the
application, the interfaces of the application, what the application will do or how the application
will connect with the outside clients, the requirements under which it will work. This Software
Requirement Specification report will give an unmistakable comprehension of what is normal by
the customer in the proposed RoomMaster software. This will give an unmistakable thought on
how the product ought to be created by the improvement group for the end clients. This SRS will
give a strong base or establishment for the venture. From this SRS, the originators can
configuration low-level outline reports and the analyzers can make test arranges and different
experiment archives. The primary objective of the venture is to plan an adaptable and extensible
framework for dealing with the exercises. The application will be outlined with the client driven
approach that will guarantee that the client necessities said in the reports must be full filled and
should adjusts to the required gauges[Mic95].
Functional Requirements: Useful necessities for the purpose application which describe the
important events of the software comprise all the data of the invention fundamentals for the
improvement of the booking softwarefor RoomMaster extend.
1. Customer interface useful necessities
2. Management group interface
Login capacity: The framework might permit just administration colleague to get
to the specific framework. ROOMMASTER 3 View or alter: The software should permit administration part to check client’s details.
3. Booking: The framework might record all the accompanying data of client.
4. Database Administrator: The application ought to permit administrator clients to get to
the framework just with username and watchword. The software also permit
administrator clients to alter any records and organizers.
Programming Interfaces: The software might interface with an Oracle or Access database.
Equipment Interfaces: The application might keep running on a Microsoft Windows based
system.
Communication Interfaces: The framework should be an independent item that does not
require any correspondence interfaces[Kar13].
Nonfunctional Requirements: Functional necessities characterize the necessities as far
as execution, legitimate database prerequisites, plan imperatives, principles consistence,
unwavering quality, accessibility, security, practicality, and movability.
Execution Requirements: Performance necessities characterize adequate reaction times
for framework usefulness
Outline Constraints: The RoomMaster System might be persist private application
running in a Windows situation. The application might be produced used Java and an
Access or Oracle database. Standards Compliance There should be stability in factor
names inside the application. The graphical user interface might have a steady
appearance and feel.
Trustworthiness: Identify the variables required to build up the required unwavering
quality of the product framework at time of delivery.
Availability: The application should be accessible among usual lodging working hours.
Security: Customer service representative and administrator will have the ability to sign
into the RoomMaster System. Client Service Representatives will have admittance to the
Reservation/Booking. Directors will have admittance to the Management subsystem and
in addition the Reservation/Booking and Food subsystems. Maintainability: The ROOMMASTER 4 RoomMaster System is being produced in Java. Java is a question situated programming
dialect and should be anything but difficult to keep up
Portability: The RoomMaster System should keep running in any Microsoft Windows
condition that contains Java Runtime and the Microsoft Access database[Law09].
System Architecture: Programming application structural design is the way toward
describing a systematized planning that meets the greater part of the specific and
operating necessities, while streamlining basic feature characteristics, for example,
execution, security, and reasonability. It includes a development of varieties in light of a
wide variety of elements, and each of these choices can have impressive effect on the
quality, execution, viability, and general achievement of the application. In RoomMaster
software we use Event-Based Architecture.
Event based, Implicit Invocation: Generally, in a software in which the segment
interfaces give an accumulation of methods and capacities, segments cooperate with each
other by unequivocally conjuring those schedules. In any case, as of late there has been
extensive enthusiasm for an option mix procedure, differently alluded to as verifiable
conjuring, responsive coordination, and specific communicate. This style has recorded
roots in software in view of performers, limitation fulfillment, daemons, and bundle
exchanged systems. The thought behind understood summon is that as opposed to
conjuring a method straightforwardly, a part can declare at least one occasions. Different
segments in the software can enlist an enthusiasm for an occasion by partner a system
with the occasion. At the point when the event is declared the software itself conjures the
majority of the techniques that have been enlisted for the event. Accordingly, an event
occurrence implicitly causes the summon of strategies in different modules. One essential
advantage of verifiable conjuring is that it gives solid bolster for reuse. Any part can be
brought into a software basically by enrolling it for the occasions of that framework. A ROOMMASTER 5 moment advantage is that understood summon facilitates software advancement.
Segments might be supplanted by other segments without influencing the interfaces of
different parts in the software[Dav94].
Software Design
Software design is exceptionally imaginative stage in programming advancement where the
designer decides: How the framework or program ought to meet the client's needs.
How to make framework successful and effective. To design a software mainly, two approaches are used: Function oriented and object oriented. To
design RoomMaster software we will used function-oriented approach. In function-oriented
approach, design is deteriorated into set of communicating units where every unit has plainly
characterized work[Hon05].
The main functional areas of RoomMaster software are Products, Pricing, Download, Support
and Training, Remote access, Features, Booking Engine. ROOMMASTER
Use case diagram: below is a use case diagram which shows the functionality of RoomMaster
software with Customer, manager, and receptionist. 6 ROOMMASTER
Class diagram: below is class diagram is shown which show the room booking procedure. 7 ROOMMASTER 8 References
Jackson, M. J. (1995). Software Requirements & Specifications. ACM Press.
Karl Wiegers, J. B. (2013). Software Requirements. Pearson Education.
Lawrence Chung, J. C. (2009). Non-Functional Requirements in Software Engineering . 17.
Shaw, D. G. (1994). An Introduction to Software Architecture. 42.
Zhu, H. (2005). Software Design Methodology. Butterworth-Heinemann.
InnQuest Software. (1994). InnQuest Software. Retrieved from
http://www.innquest.com/roommaster/
Rangel, D. (2016). Devops: Learn One of the Most Powerful Software Development
Methodologies Fast and Easy. CreateSpace Independent Publishing Platform. CSC424(JAN2017FT-1) - Module 1 Session Long Project

Attachments:

• 1493691991-SDP.docx