SBM4201 System Analysis And Design

NSW car Rental Company

This portfolio is about a NSW car rental company that mainly deals with renting of their vehicles to their customers where they book through the company’s staffs, however the company has a database that records the details of the vehicles ,customers and the staffs in the varies database tables as illustrated in the below entities, attributes and entity relational diagram.

Identification of entities and attributes

Below are the various NSW car rental company database entities and the respective attributes.

Entity	Attributes	Data types	Size	Constraints
Staffs	Staff_ number  First_name last _name street_number street_name suburb  post-code city state gender date_of_birth office_number office_phone_number	Int Varchar Varchar Int Varchar Varchar Varchar Varchar Varchar Varchar Date Int Int	20 20 20 20 20 20 20 20 20 20 20 20 20	Primary key
Customers	Customer_number  First_name Last_name Street_Number Street_Name Suburb  Post-Code City State Gender Date_Of_Birth Telephone_Number License_Number	Int Varchar Varchar Int Varchar Varchar Varchar Varchar Varchar Varchar Varchar Int Int	20 20 20 20 20 20 20 20 20 20 20 20 20	Primary key
Vehicle	Car_Registration_no  Make  Model  Colour_of_vehicle  Rental_price_per_day	Int Varchar Varchar Varchar Int	20 20 20 20 20	Primary key
Bookedcars	Bookingno Car_Registration_no Customer_number Date_borrowed Return_date Total_cost Staff_number Terms_and_condition	Int   Int Date Date Int Int varchar	20 20 20 20 20 20 20 20	Primary key Foreign key Foreign key       Foreign key

(Singh, 2016)

Question one: customer database for the Max league baseball team

In this portfolio a project that involves creating of the customer database for the max league base ball team is to be implemented through the various steps of system development life cycle and they will involve various activities where each and every activity is covered within a specific set of time frame in order to ensure that the system had been completed within the set time limit.

Below are the work breakdown structures, the start and finish dates for the project implementation (Wixom, 2016).

Work breakdown structure  

Task Name	Duration	Predecessor
System design	5 days	-
subsystem A design	5 days	System design
subsystem B design	4 days	subsystem A design
subsystem C design	5 days	subsystem B design
Program A	9 days	subsystem C design
Program B	5 days	Program A
Program C	8 days	Program B
Testing	4 days	Program C

Start, finish date for each task and the critical path 

TASK	Start date	Finish date
System design	3/9/2018	7/9/2018
subsystem A design	8/9/2018	12/9/2018
subsystem B design	13/9/2018	16/9/2018
subsystem C design	17/9/2018	21/9/2018
Program A	22/9/2018	30/9/2018
Program B	1/10/2018	5/10/2018
Program C	6/10/2018	13/10/2018
Testing	14/10/2018	18/10/2018

Question Two: IS project manager for a software developing

In this portfolio a project that involves creating of the IS software system project that is to be managed by the project manager and it will be implemented through the various steps of system development life cycle and they will involve various activities where each and every activity is covered within a specific set of time frame in order to ensure that the system had been completed within the set time limit.

Below are the work breakdown structures, the start and finish dates for the project implementation.

It starts with research (15 days), understanding system requirements (14 days), install required applications (7 days), writing algorithms and coding (20 days), debugging and testing (8 days) and finally deploying and maintained (5 days)

Work breakdown structure  

Task Name	Duration	Predecessor
Research	15 days	-
understanding system requirements	14 days	Research
Installing required applications	7 days	understanding system requirements
writing algorithms and coding	20 days	Installing required applications
Debugging and testing	8 days	writing algorithms and coding
Deploying and maintenance	5 days	Debugging and testing

Start, finish date for each task and the critical path 

TASK	Start date	Finish date
Research	3/9/2018	17/9/2018
understanding system requirements	18/9/2018	1/10/2018
Installing required applications	2/10/2018	8/10/2018
writing algorithms and coding	9/10/2018	28/10/2018
Debugging and testing	29/10/2018	4/11/2018
Deploying and maintenance	5/11/2018	9/11/2018

Question one: Car Rental System

This portfolio covers the car rental system design which is a new system to be used by the carhire which is a car rental company in Australia since 2010.

In this the various services will be implemented in the company which includes the database management systems and networking server, installation of network infrastructure and also development of the mobile system which will all be implemented in the carhire project.

Below are the various processes to be used in the system implementation which are illustrated in the system development life cycle.

System development life cycle

1. Identifying the problem.

This stage is where the company current system is analyzed to identify the problem in it and justify need for the new system where the car rental system will be selected as the possible solution this stage is will take a period of 3 days.

2. Planning and monitoring the project.

This is the second stage after identifying the problem where the project manager is involved to outline the various possible activities, how they can be done and organizing the experts to do those tasks, in this case the time required will be 4 days.

3. Gathering the system requirements.

In this stage the system analysts will be involved and they will be able to gather the requirements to implement the database system, network infrastructure and mobile application and this will take a total of 7 days.

4. Designing the system’s components.

This is the stage that will be done after the gathering of system requirements and it will be carried out by the system designers where the various project segments will be designed to make a foot print for the system building and this stage will cover a total of 5 days( Gupta, 2015).

5. Building, testing, and integrating system’s components.

This is the fifth stage which will be carried out after the designing of the system components where the system developers, network designers and app developers are involved to build, test and then integrate the project components where it will be completed within 4 days.

6. System deployment and maintenance.

This is the final stage of the system development where the entire system is deployed and then it is tested further to test some problems which are repaired as part of system maintenance and this stage takes a total of 15 days.

Work breakdown structure  

Task Name	Duration	Predecessor
Identifying the problem.	3 days	-
Planning and monitoring the project.	4 days	Identifying the problem.
Gathering the system requirements.	7 days	Planning and monitoring the project.
Designing the system’s components.	5 days	Gathering the system requirements.
Building, testing, and integrating system’s components.	4 days	System deployment and maintenance.
System deployment and maintenance.	15 days	Building, testing, and integrating system’s components.

System Assumptions

Below are some of the assumptions made in the car rentals system.

1. All the system users must have login details.
2. The system should enable the users to send and receive emails.

• The staffs, students and customers will be able to access rental details through the website.

1. The customers will be able to install mobile application in their phones regardless of the platform (Goyal, 2011).
2. The customers will be able to search and book the car using the mobile application.

Sydney Dentist Centre system migration test plan strategy

The Sydney dentist centre currently uses the old system of storing information in the Microsoft office access database and they currently aims at improving their record storage by migrating their records to new database system of Microsoft SQL server database management system (Longworth,2012).

Below are the plans that will be used to test the migration tool before it is fully deployed and testing the success of the database migration.

Test plan tools/strategy

To successfully deploy the system database without any error below are the major test plan steps to be used.

Step1: Test Database Integrity

The database will be tested for its integrity before the migration process and this will cover the following:

1. Unit testing the schema’s objects.
2. Verifying that data elements are created according to the mappings.

• Verifying that all the constraints are well in place.

1. Ensure that the function, trigger, and stored procedure had been transformed with accuracy.
2. Verifying the data accessibility.

Step 2: Test Security

The SQL server databases system has different type of security systems with the Microsoft office access database and thus different ways of authentication are used in login in the database systems where passwords will be required to manage the database, moreover there will be requirements of windows authentications or use of database authentication .Therefore the  security tests will be done to ensure that the access database had mapped the SQL server database users ,roles and objects accordingly (Downs, 2011).

Step 3: Validate Data

In the data migration the database index and the constraints tend to affect the performance in the process of migration of data, however during the migration process if the triggers are fired will end up corrupting the data and end up in production of undesirable results. Therefore before the migration is done the stored data will require to be checked and ensure that it is correct and complete during the migration and also it will be validated after it is migrated (Jain, 2010).

Identifying whether the tests is passed

After the migration of the database from the Microsoft access to Microsoft SQL server the new database is to be tested in whole where the various aspects will be covered including the database architectures, objects, data, and user, connectivity, security and performance tests and this will be achieved using the process to validate the migration below.

Checking passed tests

The following validations will be done to test whether the test plan is passed.

• Checking the records count if they are same in old and new database.
• Checking whether the data types of the both database are same.
• Comparing the summary of the report for the both databases.
• Checking the ad-hoc controls totals.

The test plan will be “passed” if all the above validations are successful else there was an error in the database migration process (Laplante, 2013).

Reference 

Laplante,P.(2013).Real-Time Systems Design and Analysis: Tools for the Practitioner. New Jersey:Wiley.

Jain,S.(2010). A Level Made Simple Structured System Analysis and Design. New Delhi:Bpb Publications.

Downs, E.(2011). Structured Systems Analysis and Design Method: Applications and Context. New Jersey: Prentice-Hall.

Longworth, G.(2012). Introducing Structured Systems Analysis and Design Method. New Jersey: Blackwell Publishers.

Goyal, A. (2011). systems Analysis and Design Paperback.INDIA:Prentice Hall India Learning Private Limited.

Gupta,B.(2015). Power System Analysis and Design.New Delhi: S Chand & Company.

Singh,B.(2016). Systems Analysis and Design.Delhi:New Age International Private Limited.

Wixom,D.(2016). Systems Analysis and Design.New Jersey:Wiley publishers.