Summary: I have prepared use case diagram for the given situation. Combined with the use circumstance diagram, I have prepared specs for individual use circumstances. Besides, I have prepared an activity diagram.
(a) School Diagram
-Staff ID
Staff
+Create new staff
-Staff Name
+Delete existing staff
+Update staff
Clerical Assistant
-Clerical Assistant ID
-Clerical Helper Name
- Clerical Associate Contacts
-Join Date
+ Print out address label
+Record customer details
+Print ticket and sale ticket
Station Master
-Station Professional ID
-Station Professional Name
-Station Master Contacts
-Join Date
+ Provide hand at hand ticket
+Record ticket type details
Rail way manager
-Manager ID
-Manager Name
-Manager Contacts
-Join Date
+ Record time details
+Record engine details
Ticket Booking
-Customer ID
-Booking date
-Booking rate
+ Create Booking
+ Delete Booking
Customers
-Customer ID
-Customer Name
-Customers contacts
+ Give Tickets
+ Give requirements
+ Get booking
Booking via mail
-Customer ID
-Booking date
-Booking rate
+ Create Booking
+ Delete Booking
Booking over telephone
-Customer ID
-Booking date
-Booking rate
+ Create Booking
+ Delete Booking
Booking In person
-Customer ID
-Booking date
-Booking rate
+ Create Booking
+ Delete Booking
Figure 2. 1: School Diagram
(b) Qualities and methods:
Class Name: Personnel.
Attributes:
Staff ID
Staff Name
Method:
Create new staff()
Delete Existing Staff()
Update existing Staff()
Class Name: Railway manager
Attribute:
Manager ID
Manager Name
Manager Contacts
Join date
Operations:
Record time details()
Record engine details()
Class name: Place Master
Attribute:
Station master ID
Station grasp Name
Station master connections.
Join date
Operations:
Provide hand to hand tickets()
Record solution type details()
Class name: Clerical Assistant
Attribute:
Clerical Assistant ID
Clerical Helper Name
Clerical Assistant connections.
Join date
Operations:
Print address brands()
Record customer details()
Print and sales solution ()
Class name: Customer
Attribute:
Customer ID
Customer Name
Customer contacts.
Operations:
Give tickets()
Give requirements()
Get arranging()
Class name: Ticket Booking
Attribute:
Customer ID
Booking date
Booking rate
Operations:
Create Arranging ()
Delete Booking()
Class name: Booking in person
Attribute:
Customer ID
Booking date
Booking rate
Operations:
Create Booking ()
Delete Booking()
Class name: Booking over telephone
Attribute:
Customer ID
Booking date
Booking rate
Operations:
Create Booking ()
Delete Booking()
Class name: Scheduling via email.
Attribute:
Customer ID
Booking date
Booking rate
Operations:
Create Scheduling ()
Delete Booking()
Summary:
I have prepared a school diagram and described the attributes and methods for every of the classes.
Task 3
Introduction:
In this, I must make three different diagrams predicated on analyzing the system. These three diagrams will be behavioral models using subject oriented method.
Sequence diagram:
A sequence diagram is a model demonstrating sequences of occurrences and interactions that happen within several layers and persons within the machine. In need of behavioral modeling, series diagram really helps to understand relevant action of the actual system. Following diagram shows the sequential diagram for the suggested system.
Sequence Diagram
Staffs
Request for ticket booking
Check Arranging Info
Check customer info
Request customer details
Give customer detail
Choose ticket
Confirm ticket booking
Figure 3. 1: Series diagram
State Machine:
State machine is near to activity diagram. Whereas in activity diagram, connections are displayed, here the state of the different layers of the system is displayed. Pursuing diagrams demonstrates point out machine diagrams for solution control and providing it to customers hand to hand, to address or via mail.
Requesting ticket booking
Checking ticket availability
Ticket not available
Cancel
Provide solution information
Make selection of ticket
Ticket not chosen
Cancel
Print ticket
Provide solution to customer
Figure 3. 2: Express Machine Diagram
Communication Diagrams:
2. Go for customers () 2. 1. Show customers ()
3. Select Solution Availability () 3. 1. Show ticket availability ()
4. Choose solution () 4. 1. Show solution ()
1. Start UI
: Ticket booking
: Ticket booking
<>
<>
3. 2 Get solution information ()Staff
4. 2 confirm ticket booking
2. 2 Get customers details ()
: Ticket booking
: Customers
<>
<>
Figure 3. 3: Communication Diagram
Summary: I've prepared three different diagrams representing behavioral modeling of the suggested system.
Task 4
Introduction:
In this, I must demonstrate the info protection regulations available in the locality. Besides, I have to describe how they can be implemented. This discourse needs to be practical enough on the other hand with the real scenario.
Some words on data cover laws:
Data protection laws and regulations package with the intellectual property of any group. In an over-all sense, this discussions about how the intellectual property should be secured and what will be took place if the info is harmed. And if it is deliberate, then what process will be used to prevent any more approach. Data safeguard laws in a way is a vital way that establishes guarantee to safeguard any company's intellectual property.
(a) Our countries scenario with data cover laws:
Unfortunately, inside our country there are no governmental data safety regulations available. Since protecting intellectual property is the major thing for just about any company, organizations use their own protocol for protecting data. Big IT based mostly companies across the country have their individual data protection laws.
Following sections cover data safeguard management available in our country-
Accessibility Restriction: Ease of access within a specific system area depends upon administrators, which prevent incorrect persons to be in a wrong place. Anybody with no prior knowledge on any progress part of a system can damage it even though unintentionally. Within the area of confidential data options, not everyone should be allowed to access.
User Authentication: After guaranteeing minimal user restriction, establishing individual authentication allows the system to be secured from unauthorized activity. Something is bound within limit; users are bound with limitations of use or activities, which lead into the necessity of user authentication.
Distribution of level: This is another major procedure by which it is ensured that there are multiple degrees of the system within which multiple levels of users are permitted to do activity.
System Security: System must be shielded both literally and logically. Tickets room must be preserved from free gain access to. Data stored should be encrypted. Disk partitions utilization should be restricted to bare minimal.
(b) Implementation of protection laws and regulations against the railway's system:
The computer system being developed can be secured by implementing one of the above-mentioned ways. Following points cover some of the ways that would be sufficient for the railway:
The most functional way is customer authentication method. To gain access to the system, individual has to enter into the account. The security password should match size and complexity requirements. This authentication method can protect the machine from any unauthorized access of the machine.
Different degree of authentication can be implied. While someone is trying to breach the machine, he may find one of the passwords, but not likely are certain to get all to breach all the info.
Level of ease of access is another methodology highly effective for the new system. Administrator will have the full access when other will have limited access within their usage limitation.
(c) Ensuring data cover in today's system:
Testing: Tests all the security process potentially available and designed for the existing system.
Validation: Validation strategies would be establish for the system. When users will try to enter the machine with passwords and usernames, system will check for validity and authorization limitation.
Encryption: System will are capable to encrypt potential delicate data. This will likely protect data from being presented to an incorrect hand.
Summary:
I have collected information on security and coverage laws and request of the laws and regulations with the existing system. Possible information on methods that may be implemented for the current system are also given.
Task 5
Introduction:
In this, I must demonstrate the system's capacity for preparing seat tickets. Along with preparing tickets, I also have to describe that how the system can prepare seat tickets that cannot be copied easily and you will be easy to printing with affordable printing medium. Besides, I also need to summarize the hardware related to printing by researching available options.
New system will mainly offer with the seat tickets. Preparing seat tickets is one of the major jobs with safety features from being copied. Pursuing section shows some methods by which tickets can't be copied-
Copy elimination methods:
In each solution, ticket creator gives a 12 digit amount as a barcode. Each and every time ticket's barcode will be inspected by checker software or barcode scanner.
Ticket should not be paper on any typical paper. Each ticket will be published on particular printing paper that's not likely to be copied or available.
Each ticket will carry specific customer's identification along with the seat number. Every fine detail must be unique within all the seat tickets.
Practically watermarks receive with typical software. So, special watermark should be paper on the ticket.
Specialized hologram is another way to safeguard ticket from being copied.
Allowing customers to select multiple tickets of different kinds:
There are several steps here to allow customers to make choice from different kinds of ticket.
In person: When place master will offer with the booking of a solution, he will deal with a person face to face. Customer can practically look over available tickets and make choice that suits them the most.
Via cell phone: When a client will get connected through the mobile phone, then clerical assistant provides with enough information. When customers will ask clerical associate for ticket booking, assistant will provide available options after knowing the destination of the clients.
Via email: When customers will obtain a solution via email, clerical assistant will record the email. Then he will send a give food to back giving all detailed options that exist. Then after handling all data, chosen solution will be affirmed.
Printing hardware and media details:
For printing the tickets, several system components will be necessary. Printers, stamping servers, computer systems will be necessary. Among the conventional products for these purposes, there are so many which is often used here to determine the printing service for the labels and tickets.
Details of suggested standard product for printing
Device
Vendor
Price ($)
Computer
HP
500
Ticket Printer
HP
150
Computer maintenance
250
Application software
Atlas designer ltd.
250
Power Supply
200
Printing Server
1000
Figure 5. 1: Hardware details
Brief details of some components:
Application Software:
Application software for organizing tickets and stamping them on a media is custom-made software developed by a conventional creator. Instead of buying mass market software, it's better to have one specifically made for specific goal. This will also be a much better option for security issue
Ticket printers:
Rather than setting up general goal printers, solution printers are suggested to be used. Solution printers are specially designed for printing tickets. Following image shows an average ticket printer-
Figure 5. 2: Ticket Printer
Printing Server:
Printing server is an average server installed for printing purposes. This server is made by personal computers.
Summary:
I have exhibited several issues on printing and printing mass media for ticket serving purposes. I have also mentioned about the hardware that may be set to establish system for stamping those seat tickets.
Task 6
Introduction:
In this, I have to put together several normalized stand with relevant information within different levels. After completing normalization tables, I must prepare data dictionary entries for all those items contained in the data source design.
Task 6 (a)
Ticket arranging normalization:
Normalization identifies dividing a data source into several tables to determine their relationship among each other.
Data Aggregation:
Serial No.
Booking Type
Customer ID
Customer Name
Customer Address
Date
Staff Type
Staff ID
Staff Name
Seat No.
Total.
2. Choosing key: Serial No.
3. Transforming to 1NF (Taking away repeating data):
Serial No (PK)
Booking name
Booking type
Customer Id
Customer name
Customer address
Date
Staff type
Staff Id
Staff name
4. Converting to 2NF (Taking away Partial Key Dependency):
Serial No (PK)
Booking name
Booking type
Customer Id
Customer name
Customer address
Date
Staff type
Staff Id
Staff name
5. Converting to 3NF (Removing non-key dependency):
Ticket Booking
Serial No (PK)
Booking name
Booking type
Customers:
Customer Id
Customer name
Customer address
Date
Staff
Staff type
Staff Id
Staff name
Task 6 (b)
Data Dictionary for Customer:
Data dictionary
Railway
System:
S5D
Type: structure Name: customer
Alias
: Client
Definition:
Customer=
customer Identification+
customer name+
Customer connections+
Occurrence:
Picture:
Author:
Rajan Khan
Date
10. 2. 2011
Figure: Data dictionary for customers.
2. Data dictionary for staff
Data dictionary
Railway
System:
S5C
Type: structure Name: Staff
Alias
: employee
Definition: Personnel:
Staff Identification+
Staff name+
Staff Contacts
Occurrence:
Picture:
Author:
Rajan Khan
Date
10. 2. 2011
Figure: Data Dictionary for Staff
3. Data dictionary for ticket booking.
Data dictionary
Academic
theater
System:
S8c
Type: structure Name: Solution Booking
Alias
Definition: Ticket reservation :
Ticket serial No+
Ticket Booking day+
Ticket Booking rate+
Occurrence:
Picture:
Author
Rajan Khan
Date
10. 2. 2011
Figure: Data Dictionary for solution booking
Summary:
I have completed normalized data dining tables and dictionary entries for all your items that will be contained in the database.
Task 7
Introduction:
In this, I must remark the objected oriented methodology for building system or growing system. Besides, I have to associate my remarks with the machine design that I have done for the prior jobs. Then, along with explaining object driven methods, I also have to remark structured methods.
Differentiation between both methods:
For Job 1:
Object Oriented: For designing diagrams in activity 1, use case diagram and activity diagram are being used. For analyzing every fine detail use circumstance diagram include detailed specification.
Structured: As per the requirements stated in organized diagram, DFD (Data Movement Diagram) could solve the problems of job 1.
For task 2:
Object Oriented: Since subject oriented methods are basically reliant on object-class architecture, here school diagram can be used.
Structured: In set up strategy, ERD (Entity Romantic relationship Diagram) is used.
For task 3:
Object Oriented: Here the collection and communication diagram are widely-used.
Structured: Here the ELH (Entity Life Record) would be utilized.
Object Oriented Methods:
Advantage:
System can be quite large. In thing focused method, modularization divides whole system into several workable smaller parts or items. In that way, when parts are developed, they can be synchronized to help make the whole system working.
Object driven applications are definitely more scalable than the organized tools.
With looking at the modules of the system, you'll be able to make a synopsis on how the machine is likely to be.
Disadvantage:
Legacy Systems are designed in structured development languages. So when it is necessary to convert those systems, it becomes a tough job.
Object Oriented Databases Management Systems are not available.
Since there are many choices with object focused methodology, sometimes unpredicted confusion can surge.
Structured Methods:
Advantage:
In structured coding, system requirements are described much before encoding starts.
With proceed of development, amount of necessary changes starts to diminish.
Disadvantages:
Every aspect should be prepared and structured. Without the direct link, it's impossible to use a random manner, unlike the object oriented.
Overview of a system before it is developed is not likely to be accessible.
Summary:
I have remarked benefits and drawbacks of both structured and object oriented technique. Besides, I've remarked the application of both the technique with job 1 to job 3.
Task 8
Introduction:
In this task, I must produce a detailed report with detailing all the responsibilities that I have completed. I QUICKLY must make an appendix reviewing my works.
Executive Summary
Preparing functional modeling:
This includes two diagram and one standards details for one of the diagrams.
Use case diagram (With Specification)
Activity Diagram.
Structural Modeling:
Class Diagrams.
Detailed attribute and businesses.
Behavioral Modeling:
Sequence diagram
State machines
Communication Diagrams.
Data Cover issues:
Available data safety laws.
Implementation of the issues with the machine.
Safe solution management:
How to create safe seat tickets.
How the customers will be able to select multiple options.
What hardware will be used to print the tickets?
Relational database creating:
Creating normalized furniture.
Creating data dictionary.
Evaluating object oriented method:
Advantage and down sides of object oriented methods.
Contrasting with organized method.
Report
Within all the phases of the tasks, several planning and evaluating have been done. Within this report, most of them will be included for an improved demonstration. Following section covers thorough details of job 1-7 respectively.
Task 1: Functional Modeling
Use circumstance diagram for railway management system:
Use case diagrams are useful to understand the system from the point of view of user. On this part there are three objects. There are customers, clerical helper and ticket scheduling. Customers request for the ticket booking then clerical assistant check ticket information and clerical assistant get booking information. Clerical helper question to customer their information then customer give details information and customer choose ticket set. At a final customer confirm ticket arranging to clerical assistants.
Several use circumstance diagrams could be place into the scenario. But one compact use circumstance diagram can be used to protect potential top features of the system somewhat than creating multiple diagrams. It has saved lots of time.
Activity Diagram for Railway Management System:
Railway management's potential activities are shown in this diagram. Railway manager will record the time information and hauling engine information, station grasp will sale ticket hand at hand and clerical assistant will provide through mail or cell phone- everything is protected in this activity diagram.
Task 2: Structural Modeling
Class Diagrams:
Several classes are available from the suggested system. Course diagrams are drawn based upon those classes found from the railway management system's scenario. These classes include attribute and procedures details within each of the class.
Task 3: Behavioral Model
Sequence Diagram:
This diagram describes the sequential demonstration of occurrence within the system. By the help of this diagram, expected action of the machine can be recognized. Comprehensive presentation of all persons getting together with the system in a move established order; this really really helps to understand the system
State machine diagram:
This diagram shows the state governments of the functions. From taking time details to control ticket reservation, every state is identified in this diagram. This plainly shows the end of activity.
Communication Diagram:
In this top order diagram, only the primary procedure and interacting people are shown in a thorough and technological way.
Task 4: Data Security Issues
Our countries scenario:
Big IT centered companies across the country have their individual data protection regulations.
Accessibility Restriction: Convenience within a particular system area depends upon administrators, which prevent incorrect persons to be in an incorrect place. Any person with no previous knowledge on any progress part of a system can cause damage to it even though unintentionally. Within the region of confidential data resources, not everyone should be allowed to access.
User Authentication: After making sure minimal user restriction, establishing individual authentication allows the system to be safeguarded from unauthorized activity. A system is bound within limit; users are destined with limits of consumption or activities, which lead in to the necessity of individual authentication.
Distribution of level: That is another major approach where it is guaranteed that we now have multiple levels of the system within which multiple degrees of users are permitted to do activity.
System Security: System must be safeguarded both physically and logically. Tickets room must be preserved from free access. Data stored should be encrypted. Disk partitions utilization should be limited to bare minimal.
(b) Execution of protection laws and regulations against the railway's system:
The computer system being developed can be secured by applying one of the above-mentioned ways. Following points cover some of the techniques would be sufficient for the railway: One of the most usable way is end user authentication method. To gain access to the system, user has to type in the username and password. The security password should match period and intricacy requirements. This authentication process can protect the machine from any unauthorized gain access to of the machine.
Different degree of authentication can be implied. While a person is wanting to breach the system, he might find one of the passwords, but not likely are certain to get all to breach all the info.
(c) Ensuring data cover in the current system:
Testing: Testing all the security method potentially available and prepared for the existing system.
Validation: Validation techniques would be placed for the machine. When users will try to enter the system with passwords and usernames, system will look for validity and authorization limitation.
Encryption: System will are capable to encrypt potential sensitive data. This may protect data from being presented to a wrong hand.
Task 5: Assessing ticket control procedure
Copy elimination methods:
In each solution, ticket creator will give a 12 digit amount as a barcode. Every time ticket's barcode will be inspected by checker software or barcode scanning device. Ticket should not be paper on any typical newspaper. Each solution will be branded on special printing paper that is not likely to be copied or available. Each ticket will carry individual customer's identification along with the seat quantity. Every aspect must be unique within all the seat tickets. Practically watermarks receive with regular software. So, special watermark should be published on the ticket. Specialized hologram is another way to protect solution from being copied.
Allowing customers to select multiple seat tickets of different types:
There are several techniques here to permit customers to make choice from different kinds of ticket. When station expert will offer with the booking of a ticket, he will offer with a person in person. Customer can almost look through available seat tickets and make choice that suits them the most. When a client will get connected by having a phone, then clerical assistant will provide with enough information. When customers will ask clerical helper for ticket arranging, assistant will provide available choices after knowing the vacation spot of the clients. When customers will request for a solution via email, clerical helper will record the e-mail. Then he will send a supply back by giving all specific options that exist. Then after handling all data, chosen ticket will be validated.
Printing hardware and media details:
For printing the tickets, several system components will be necessary. Printers, producing servers, personal computers will be necessary. Among the traditional products for these purposes, there are so many which may be used here to establish the printing service for the labels and seat tickets.
Device
Vendor
Price ($)
Computer
HP
500
Ticket Printer
HP
150
Computer maintenance
250
Application software
Atlas builder ltd.
250
Power Supply
200
Printing Server
1000
Brief information on some components:
Application software for preparing tickets and printing them on a media is custom-made software produced by a conventional developer. Instead of buying mass market software, it's better to have one specifically made for specific goal. This will also be a much better option for security issue Rather than putting in general goal printers, solution printers are recommended to be utilized. Ticket printers are specially made for printing seat tickets.
Task 6: Normalization and data dictionary
Normalization:
Here database is scattered into several dining tables to determine human relationships within each of them.
Data Dictionary:
Data dictionary is build with entries from all the items which will be contained in the database.
Task 7: Analyzing Subject Oriented Methodology
Differentiation between both methods:
For Task 1: For developing diagrams in activity 1, use case diagram and activity diagram are utilized. For examining every fine detail use circumstance diagram include in depth specification. According to the requirements explained in organised diagram, DFD (Data Circulation Diagram) could solve the problems of process 1.
For task 2: Since object oriented methods are nearly reliant on object-class structures, here school diagram can be used. Structured: In organized technique, ERD (Entity Romantic relationship Diagram) is used.
For process 3: Here the collection and communication diagram are utilized. Here the ELH (Entity Life Background) would be used.
Object Oriented Methods:
Advantage: System can be very large. In object driven method, modularization divides complete system into several workable smaller parts or things. In that way, when parts are developed, they can be synchronized to help make the whole system working. Object driven applications are more scalable than the organised tools. With looking at the modules of the system, it is possible to make a synopsis on how the system is likely to be.
Disadvantage: Legacy Systems are designed in structured encoding languages. So when it is necessary to convert those systems, it becomes a tough job. Object Oriented Data source Management Systems are not available. Since there are many selections with object driven methodology, sometimes unforeseen confusion can surge.
Structured Methods:
Advantage: In organised programming, system requirements are identified much before development starts. With proceed of development, amount of necessary changes starts off to diminish.
Disadvantages: Every detail should be prepared and structured. Without the direct link, it's impossible to go in a random manner, unlike the object oriented. Summary of something before it is developed is improbable to be available.
