This action might not be possible to undo. Are you sure you want to continue?
CASE TOOLS LAB
0 0 3 100
Prepare the following documents for two or three of the experiments listed below and
develop the software engineering methodology. 1. Program Analysis and Project Planning. Thorough study of the problem – Identify project scope, Objectives, Infrastructure. 3. 4. Software requirement Analysis Data Modeling Describe the individual Phases / Modules of the project, Identify deliverables. Use work products – Data dictionary, Use diagrams and activity diagrams, build and test lass diagrams, Sequence diagrams and add interface to class diagrams. 5. 6. Software Development and Debugging Software Testing
Prepare test plan, perform validation testing, Coverage analysis, memory leaks, develop test case hierarchy, Site check and Site monitor.
SUGGESTED LIST OF APPLICATIONS 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Student Marks Analyzing System Quiz System Online Ticket Reservation System Payroll System Course Registration System Expert Systems ATM Systems Stock Maintenance Real-Time Scheduler Remote Procedure Call Implementation
RATIONAL ROSE A process is a set of partially orders steps intended to search a goal, in software engineering the goal is to build a software product or to enhance an existing one, in process engineering. The goal is to develop or enhance a process. In RUP (Rational Unified Process) there are organized into set of disciplines to further define the work flows and work process elements. Expressed in terms of business modeling, the software development process is a business process the RUP is a general business protocol for Object Oriented Software Engineering Process sharing a common structure, common process architecture. It provides a disciplined approach to assigning tasks and responsibilities. Within a development organization in its goal and to ensure the production of high quality software that meets the needs of its end user within a predictable schedule and budget. The RUP captures many of the best practices in modern software development in a form that can be tolerable for a wide range of product. When a software system is developed from scratch development is the process of creating a system from requirement. But once the system has taken from any further development is the process of confirming this system, to the new modified requirements. This applies throughout the system lifecycle. NEW OF CHANGED SYSTEM CHANGED
The Software process of developing either new or changes (Evolution Cycle).
SOFTWARE ENGINEERING PROCESS
engineering process is the a System from the requirement
Rational Rose helps companies overcome the e-software paradox by unifying the communities that develop software with a common visual language that accelerates the creation of flexible application with rousts, resilient architectures. RATIONAL ROSE SOFTWARE: ANALYSIS AND DESIGN: The application’s method recommends the use of static and dynamic views of a logical model and a physical model to capture the in-process products of object oriented analysis and design. Using the notations, the application enables you to create and refine these views within an overall model representing your problem domain and software system. This overall model contains Classes, Use Cases, Objects, Packages, Operations, Components Packages, Components, Processors, Devices and the relationship between them. A model also contains diagrams and specification, which provides a means of visualizing and manipulating the models elements and their model properties. It is software developed by Rational Corporation. It contains the information interface and the tools to create a visual model. In rose there are different views. A view is a perspective of a model. The FIVE different views called Architectural views are:
1. USE CASE VIEW: • • • • • • Contains the use case model, flow of events and supplementary documentations. It is contract between customer and developer It is essential for Analysis, Design the test activities It also contains activity diagrams It contains the use case diagrams It includes the threads and the processes that found the System Concurrency it is the heart if the other views that represent the required behaviors of the System.
2. LOGICAL VIEW: • • It supports the functional requirements of the System It includes the use case realizations, Class diagrams, Interaction diagrams, State Chart diagrams, and Activity diagrams
3. PROCESS VIEW: • • It address the Performance, Scalability and throughout the System It is not necessary for Single Processing Environment
4. COMPONENT VIEW: • • The Component view addresses the case of development management of Software assets, reuse, subcontracting, and shelf components. Describes the organization of static software like Course call data file components.
5. DEPLOYMENT VIEW: • • It addresses the view like Deployment, Installation and Performance. The Deployment is used for Distributed Systems only.
Name. it is also duty of the faculty to distribute the records maintain the records. It comprises of the student Roll no. this project is constructed with modularity which helps in the easy understanding of the project and instances access of the student’s data. Total. It also makes the work simpler. INFRASTRUCTURE: HARDWARE REQUIREMENTS: • • Processor: PENTIUM IV Capacity: 256MB of RAM SOFTWARE REQUIREMENTS: • Rational Rose Software PROBLEM STATEMENT: Student Mark Analysis system is used for the Students and the faculty to have an easy access for viewing the marks. The faculty will calculate the total marks and them based on the percentage obtained by the student he/she will be awarded the grades. is to generate the report card and he/she can view the report cards. OBJECTIVE: The main objective of designing and implementing this project is to enable the students and the faculties to see the marks easily. It is also the duty of the faculty to distribute the report cards. They do not have the permission to change or update the marks. It can be accessed by the teacher or the faculty who alone can change or update the marks of the students. Average. It is only the faculty who can update and view the students mark. But the administrator cannot update cards. All these processes are done efficiently and easily in this Student Mark Analysis System. Marks Obtained. Attendance Percent etc. NO: 1 STUDENT MARK ANALYSIS SYSTEM AIM: To analyze and design a Student Mark Analysis System using UML (Unified Modeling Language) diagram. the duty of the administrator.EX. the duty of the administrator is to generate the report cards to the faculty members. PROJECT SCOPE: The main scope of this project is to get the students marks and update it whenever necessary and then to display it for the Students and Faculties. Here in this the students can only view the marks if their Username and the Password are correct. ABSTRACT: This project “Student Mark Analysis” deals with the complete details of academic details of the Student. Here the role of the student is to just view the marks entered by the faculty of the teacher. MODULAR DESCRIPTION: .
Marks. SAVE GRADES: Save Grades is used to save the grade that has been allotted to Students. LOAD GRADES: The Load Grades allows us to load the updated grade to the Report card. UPDATE GRADES: This module allows the faculty to update grades and then to update the marks of the students whenever the semester of the examination results are released. Class Diagram: G e n e ra t e R e p o rt c a rd ro ll n o : in t n a m e : s t rin g a d d re s s : s t rin g m a rk s : in t t o t a l() a vg () g e n e ra t e () R e c o rd G ra d e s m a rk s : in t ro ll n o : in t c h e c k () p rin t () t o t a l() a vg () V ie w G ra d e s get pwd u s e r n a m e : s t rin g c h e c k () vie w () U p d a t e G ra d e s ro ll n o : in t u p d a t e m a rk : in t u p d a t e () Component View: Student Mark Analysis System Use-Case Diagram: . VIEW GRADES: This module allows the faculties as well as the Students to view the Grades. Total and the Average Marks obtained by the Student. This is the only module that can be accessed by the Student when the User name and the Password Matches.GENERATE REPORT CARDS: This module allows the faulty to generate the report cards that are going to contain the Student’s academic details.
Distributed Report Card Teacher Recard Grades Save Grades Upgrade Grades Load Grades Log on Administrator View grades Student Generate Report Card Collaboration Diagram: 3: Ask for student detail 5: provide report card Admin 2: Req. for report card 4: Provide the detail Teacher 6: Distribute report card Student 1: Req. for report card Sequence Diagram: .
Req. for report card
Req. for report card
Ask for student detail
Provide the detail
provide report card
Distribute report card
Activity Diagram: Distribution Of Report Card:
STUD REQ FOR REPORT CARD
TEACHER COLECTS REPORT FROM ADMIN
DISTRIBUTE TO STUDENT
Enter roll no
Enter the Average
Enter the grades
Load Report: SELECT THE STUDENT DISPLAY THE GRADE STOP Save Report: GET THE DETAILS SAVE THE GRADE sTP .
Record Details of Report: Get average if Avg<50 no if AVG<60 no if avg<=75 no if avg>75 no STOp YES fail YES c grade yes b grade yes a grade Deployment Diagram: STUDENT 3 STUDENT 2 STUDENT 4 STUDENT MARK LIST STUDENT 1 STUDENT NAME .
MODULAR DESCRIPTION: REGISTRATION: Using this module the participants can register their details to participate in the Quiz program. OBJECTIVE: The main objective behind developing this system is to handle. The scores are updated based on the positive and negative points given by the users. the intelligence. UML Components diagram which offers higher reliability and efficiency in handling the development system. The development system plays a vital role irrespective of the field of work because it has its own importance as it provides complete solution for organizing the quiz programs and to produce the results. UPDATION: This module is used to modify or update the score after verifying the answers furnished by the users. are collected from the participants. Hence lots of efforts are taken to ensure that the administration that is the participants enjoys all the benefits of the system. NO: 2 ONLINE QUIZ MANAGEMENT SYSTEM AIM: To design and develop the Quiz Management System for organizing efficient quiz Programs and to produce the results using the Rational Rose Software. All these constraints are considered and the system is developed to cater to the needs of the program organization comments. DISPLAY THE ANSWER: This field is used by the administrator to display the answer and questions. After evaluation. Details such as Name. The developing process of this system has to take care of certain important stages with a strong view that it deals with the most important instances of the world.EX. PROJECT SCOPE: The quiz management system is developed after the completion of all necessary. EVALUATION: This module is used to verify or check the answers furnished by the users. the most important system which has its roots in almost all the companies and firms with ease and necessary. Age. and Qualification etc. These enhancements and all other aspects are handled and it is tailored in such a way that it meets the needs of the administrator. Each user will be given a separate password after registering their forms. The scores are updated based on the positive and negative points given by the users. the scores are updated by administrator. . The administrator will display the next question. After getting the answers from the users for the question displayed.
Once result is announced. prizes will be distributed to the winner. WINNER LIST: This is a unique module which is used to display the list of winner at the end of the competition.ANNOUNCEMENT: This module is used to announce the result of quiz program. The winners will be honored by issuing certificate and prizes. Class Diagram: Candidate <<void>> cha name <<void>> int age <<void>> char qualification <<void>> resume() <<void>> field() Program Executive char name int marks int time int rank Accept() verify certificat() Component Diagram: Quiz System .
Use-Case Diagram: Register Display Question Participant Answer Questions Data Base Display The score Co ordinator Winner List Collaboration Diagram: 5: Select the field 6: Answer the ques 2: Display the question 4: Evaluation of score 8: Announce the result 3: Verify 1: Accept the Req from Candidate Program Execution 7: Update the score Quiz master .
Sequence Diagram: Candidate Accept the Req from Program Execution Quiz master Display the question Verify Evaluation of score Select the field Answer the ques Update the score Announce the result .
Activity Diagram: Announcement of result: Get the ans from database Announce the result Display of questions: Accept the field Display the ques Invalid field Get the ans Store the ans Store the field .
Evaluation Of Results: Accept the ans Verify the ans Update the score Update Result: accept the ans Check the ans Negative point Positive point Update the point Close the point .
Deployment Diagram: co-ordinato r online quiz system candidate database/ admin .
OBJECTIVE: The main objective behind developing this system is to handle. in this module the administrator get the no.e the individuals enjoys all the benefits of this System. NO: 3 ONLINE RESERVATION SYSTEM AIM: To design and develop the Reservation System for manipulating the reservation details of a person using Rational Rose Software. of credit card. the most important System which has its rot in almost all the banks and firms with ease and accuracy this system requesting almost. checks the money and finally issue the ticket. of seats occupied etc. The developing process of this system has to take care of certain important stages with the strong view that deals with the most important instances of the world. INFRASTRUCTURE: HARDWARE REQUIREMENTS: • • Processor: Pentium IV Capacity: 256MB of RAM SOFTWARE REQUIREMENTS: • Rational Rose Software MODULAR DESCRIPTION: AVAILABILITY: This module contains details about the number of sears available for reservation. ENQUIRY: This module contain details about the enquiry made by the users. the currency. RESERVATION: Using this module the user can reserve the tickets he need. total number of seats available for reservation. This System must be flexible in such a way that it allows ensure enhancement or modification i. . Hence lots of efforts are taken to ensure that the administrator i. PROJECT SCOPE: The Online Reservation System is develop after the completion of all necessary UML Component diagrams. the entry of new reservation detail and the removal of already existing details these enhancements and all other aspects are handled and it is tailored in such a way that it meets the need of the administrator. The developed System plays a vital role irrespective of the field of Online Reservation because it has its own importance as it provides complete solution in processing and managing the reservation details of an individual.EX. total no. this module administrators search the ticket by getting the details from the user and produce the results to the user. which offers higher reliability and efficiency in handling the developed System.e.
CONFIRMATION: Using this module the user can check whether the ticket reserved by him is confirmed or not. The administrator cancels the ticket by getting the ticket number from the user. modifies the ticket that has been reserved already. CANCELLATION: This module is used to cancel the tickets reserved by the users. The ticket is not yet reserved the user sends the requests to the administrator. Class Diagram: The user Website Char : Web Search webpage() Enquiry <<int>> ticket <<char>> passing <<int>> cardno status of card() passenger details() Reservation <<int>> dae <<char>> place <<int>> cardno date of journey() checksthe place() check credit cardno() Cancel <<int>> ticket Cancel Operation() Modify <<int>> date <<int>> passenger Change the date() int passenger() Component View: Online reservation Use-case Diagram: .MODIFY: This module contains details about the modification of the ticket reserved.
Enter the website enquiry passenger reservation system modify cancel Collaboration Diagram: Login System 1: Enter id and password 2: Login 9: Modify journey date Modify 7: Verify passenger 5: Enter The detail 8: Issue of ticket Cancel 10: Cancel 3: Status of the train ticket 6: Credit card verify 4: Avail ticket Enquiry Sequence Diagram: .
passenger System Enter id and password Login Enquiry verify Modify Cancel Login Status of the train ticket Avail ticket Enter The detail Credit card Verify Issue of ticket Modify journey date Cancel .
Activity Diagram: Activity: Enter the website Specify source and destination Choose train Specify user details Seat avail Specify card details Valid card Next train Conform ticket Display the ticket .
Cancellation: Enter THE WEBSITE ENTER THE TICKET NO ENTER TRAIN NO CONFIRM if amt refundable Enter CARD details Refund amount .
Modify: enter the website Enter train no Specify sourc and desti Enter ticket no Valid ticket yes Enter modified souce and destination Enter new train no no Confirm tick disp the ticket .
Deployment Diagram: passenger system online reservation system .
This System must be flexible in such a way that it allows future enhancement of modification i. Hence lots of efforts are taken to ensure that the administrator i. PROJECT SCOPE: The Payroll Processing System is developed after the completion of all the necessary UML component diagrams. the analysis phase was considered seriously and the design this System was developed in such a way that it provides complete Solution to all the activities of the employer. the employer enjoys all the benefits of this System. ADMINISTRATOR: . the most important System which has its root in almost all the companies and firms. The developed System plays a vital role irrespective of the field of work because it has its own importance as it provides complete solution in manipulating and managing the pay details of the employees. Likewise our ‘Payroll Processing System’ analysis phase is crucial because any single mistake made may result in heavy loss. the currency. Hence. The designing process is a tedious job when it comes to such a system which has its won risk if it is done poorly. with ease and accuracy. It is one of the important tasks that it depicts the future importance of this System.e. the entry of new employee detail and the removal of an already existing employee detail etc. This System has mainly only one actor who performs or is in charge of all activities involved in this System and that one actor is administrator. if the analysis done in the beginning does not turn out to be efficient. ABSTRACT: The analysis phase proves to be the most crucial phase in the development process of a System as it has its own impact on all other phases.e.EX. Each of the module and the activity has its own importance and the integration of all such important modules is one such a tough task which need complete guidance and advises from the expertise people who really possess a bit of experience in this field. The developing process of this System has to take care of certain important stages with the strong view that it deals with the most important instance of the world. which offers higher reliability and efficiency in handling the developed System. these enhancements and all other aspects are handled and it is tailored in such a way that it meets the needs of the administrator. OBJECTIVE: The main objective behind developing this System is to handle. NO: 4 PAYROLL PROCESSING SYSTEM AIM: To design and develop the payroll processing system for manipulating the pay details of the employees using Rational Rose Software. The designing of the flow of data i.e. It can result in re-analysis or performance of the developed System. This System requires utmost care because there should not be any errors in manipulating as well as managing the pay details of the employees of a concern. the logical flow is very crucial as this System involves quiet more number of activities and module. All these constraints are considered and the System is developed to cater to the needs of the employer.
the entire process of this System is treated with utmost care and efforts to make sure that the developed System is errorless and reliable. personal information) for effective manipulation of the pay details of that particular employee.e. Thus. The basic crux of the System has been designed in such a way that it proves to be reliable and recoverable if it happens to meet any kind of System error. EDIT EMPLOYEE DETAILS: This module is used to edit employee’s personal details as the name implies. MODIFY PAYROLL AMOUNT: This module adheres to modification made to the amount which is to be mentioned in the payroll of various employees. At the same time this system must also flexible when it comes to real time application. CALCULATE PRINT PAYROLL: This module is mainly focused with the pay details of the employees alone. Logical error and System failures. The overall performance of this System is judged in such a way that all the activities are explored and developed with great amount of interest to ensure the effectiveness of the System. This module needs to be updated only whenever a new entry comes into role lest this module task is to ensure in any list of the concern correspond to the similar data if not it indicates that there is an error. If any such happens. The main task of this module is to compute the pay details of the concerned employee and printing it. ADD EMPLOYEE DETAILS: This module caters to the needs of the administrator in adding new employee’s entrance to that particular concern in a flexible and efficient manner.The administrator deals with all the activities of this System. This module needs utmost care and this is one of the most important modules of this entire System as its failure could have a great impact on the entire System. MODULAR DESCRIPTION: This System has potentially four main modules and three modules arises from a module and therefore totally constituting seven modules and they are. This modification does may be done periodically. MANAGE TAX SALES: This module takes care of the frequent changes that are made by the government and its impact are readily absorbed by the System as it is designed in such a way to adapt to future changes. This particular field needs proper data feed and maintenance because if any edition is not updated properly then it may result in a poor result. Hence this module needs constant updation and this facility is taken care of. This particular module also needs frequent updation has its own impact on the entire structure of this System. MAINTAIN EMPLOYEE DETAILS: This module is responsible for maintaining the employee details of the concern (i. REMOVE EMPLOYEE DETAILS: . Here the flexibility refers to the amount of ease that this System delivers to the administrator in carrying out his own tasks and activities through this System. This module needs to access the payroll databases to retrieve the pay details of the particular staff. the System should not fail lest it would result in improper and wrong manipulation of the pay details which may cost more to the administrator.
Class Diagram: Manage tax rate basic-pay : int tax amount() Maintain Employee details emp-name : char Emp-id : int dept_design : char pay detail : int Maintain date() Maintain salary() Add employee details new_appointment : char dept-transfer : char branch-transfer : char add_emp detail() Calculate &print payroll emp det : char working hrs : int ot-hrs : int Leave taken : int Add-ot() add/remove amt() gross salary() Modify Payroll amt emp-dept : char promotin : char demotion : char suspension : char inc/dec basic pay() dec suspension amt() gross salary() Edit employee details ind details : char dept-details : char branch det : char Update DB() Remove employee details Retirement : char transfer : int death : int Remove emp-det() Component View: Payroll Processing . The updation is made in such a way that it is reflected in almost all the departments of the concern to make sure that the updation has resulted in a universal issues(throughout the concern). This is the prime task of this module.This module makes sure that whenever any employer resigns or quits or is fixed the employee database is updated approximately.
Use-case Diagram: Calculate & print payroll Add employee payroll Maintain employee details Payroll Operator Remove from payroll Modify payroll amount Edit employee within payroll Manage tax rates Collaboration Diagram: 2: Verify employee details 3: Maintain Employee details 4: Create employee details 9: Edit details in DB 11: Verify payroll calculate 1: Accept employee details 5: Calculate payroll details 6: Manage tax rates 7: Print pay details 8: Add /Rem Employee 10: Modify &print payroll details 12: Issue salary Employee Payroll details .
Sequence Diagram: Employee Accept employee details Payroll details Verify employee details Maintain Employee details Create employee details Calculate payroll details Manage tax rates Print pay details Add /Rem Employee Edit details in DB Modify &print payroll details Verify payroll calculate Issue salary .
Activity Diagram: Add Employee: New Appointment Dept Transfer Branch transfer No new Appointment Add details of new employee to DB Edit Employee: Update individual employee details Update dept wise employee details Update the edited employee details Maintain employee records within DB .
Maintain Employee: Employee Id_no Employee name Basic Pay Employee Dept &designation Personel Details Gross Salary Allowances Rebates & Concession Manage Tax: Emp Details Basic Pay <5000 Yes No tax Basic Pay >5000 Yes tax=10% of annual income Basic Pay >10000 Yes tax=20% of income Calculate tax amount Enter the details in payroll Enter the DB .
Modify Pay Roll: employee details Promotion Yes No demotion No Suspension Yes Yes Increment basic pay Decrement pay Calculate amount for suspended days No Reduce amount from payroll Call gross salary .
Print pay Roll: Em ployee details Working days Yes Overtime Hrs No Leave taken Yes Calculate the amount for hrs Add amount to net salary Calculate amount to nature of leave No Add/Sub amount to nature of leave Calculate the gross salary Print gross salary .
Remove Employee Details: Employee Details Yes Service retirement NO Voluntary retirement No Yes Natural/Accident al death Yes No Update transfer details in DB Yes No removed of details Remove details from DB .
academics) the analysis and development of this System must be dealt with utmost care because if anything goes wrong the students are going to be the ultimate sufferers. MODULAR DESCRIPTION: ENQUIRY: What are the courses available will be given in the enquiry. Our topic is constrained to the admission process of educational institutions. In our topic. if the candidate wants to modify or change the course. ABSTRACT: The most important phase in developing software for a customer is the analysis phase. if the candidate want to cancel the course using cancellation model.EX. This System is designed in such a way that it is completely flexible in providing two way conversations between the students and the administrator. ELIGIBLE CRITERIA: This module describes about the eligibility criteria for each course in the institutions. a modification model has been developed. This Course Registration System provides complete flexibility to the Students to choose the courses according to their desire and it also provides room for modification and cancellation of nay information or process. Each and every activities have been seriously considered and they have been implemented. The candidate can view the available courses. to enquire the available courses using enquiry model and then register the required course using registration model. As it is said that most strong and tail buildings. keeping in mind the future enhancements of this System and utmost car has been taken to solve almost all the special cases which arises due to any Special situation in the System. the Course Registration System is concerned with the process of choosing and joining the course in educational institutions.. If the candidate are eligible with the prescribed marks and percentage then they may pass to the next section of course registration otherwise their applications are rejected. There are primarily two main actors involved in this Course Registration System they are: STUDENTS AND ADMINISTRATOR: It is highly a tedious job to analyze the major modules involved in the System. The analysis phase proves to be the foundation for the Software development process. PROJECT SCOPE: The main scope of the project is to develop a Course Registration System. since this particular System deals with educational institution (i.e. NO: 5 COURSE REGISTRATION SYSTEM AIM: To design and develop the Course Registration System to enquire and to register the courses available using UML diagrams in the Rational Rose Software. REGISTRATION: . The “Course Registration System” should be more flexible for the Students (end users). It also allows the administrator to a greater extent to intimate and process the information provided by the student in an effective manner which makes this System further more effective.
the candidate can register the courses by giving his/her details. If the candidate wants to change the course. MODIFICATION: In modification model.In Registration model. he/she can cancel registration. the candidate can confirm the course and apply for it by paying the fees. ADMISSION: In admission model. Class Diagram: A dm is s ion Confirm : boolean Nam e : S ting A ge : int S ex : S tring A ddres s : S tring Cas te : S tring Confirm () Fill_A pp() E val_A pp() Course E nquiry Nam e : S tring A ddress : S tring P no : int reg() E nquiry () M odification Nam e : S tring A ge : int A ddress : S tring P hno : int m odify () fee pay() Cancellation Continuation : boolean Reason : S tring Confirm : boolean Cancel() Certi() Component View: Course Registration . if the Candidate doesn’t want to join in the Course which has been previously registered. he can change using this model. CANCELLATION: In Cancellation model. the candidate can modify his course.
Use-Case Diagram: enquiry Student Addmission Admin Modify CAncellation Collaboration Diagram: 10: Validate request 1: Enquiry Enquiry 5: Evaluate the application Student 2: Reply for register 3: getting the application 7: Fee payment Addmissio n Modificatio n 9: Request for modification 13: Validate request 4: submit the application 12: request for cancellation Admin Validate Request 6: Intimate for fee payment 8: Addmission confirmed 11: Request modification performed 14: Requetsted cancel performed .
Sequence Diagram: Student Enquiry Reply for register Enquiry Addmission Modification Validate Request Admin getting the application submit the application Evaluate the application Intimate for fee payment Fee payment Addmission confirmed Request for modification Validate request Request modification performed request for cancellation Validate request Requetsted cancel performed .
Activity Diagram: Admission: Course Confirm Application form Evaluation of appli form If eligible No Yes Rejected Addmission Fees Payment Addmission Cancelled If on date Yes Addmission confirmed No .
Cancellation: If stud is unwilling to continue the course Yes no Reason for cancel no If accepted by mgmt Yes Cancel Confirm Retreivel of certificates .
Enquiry: register Enquiry college inform structure Enquire lab facilities placement facilities Course details Fees Structure .
Modification: If modify reg No Cahnge of personel detail Change of course If confirmation Yes If seat available Yes IF fee structure No changed Yes Fee Payment No Course Confirmed .
If the code is exactly matched with the database of the customer. then the user is urged again to reenter the pin number of the access card is continued further. the users will enter the Secret code. ABSTRACT: ATM stands for Automated Teller Machine. then the transaction can be performed. If the code doesn’t match with the database of the customer. TRANSACTION: In this module. The Users can withdraw the amount from their account. the necessary transaction to be performed by the user is displayed as an option by the System. OBJECTIVE: The main objective of designing and implementing an ATM System enable the customer to have easier transaction of money at anytime without standing or waiting in queue. ATM Machine acts as an excellent technical development which provides for these users who require money anytime they require various models have been used here are: • • • • • • • Password Derived Re-enter Password Account number Deposit Withdrawal Balance Exit MODULAR DESCRIPTION. Enquiry. NO: 6 ATM SYSTEM AIM: To analyze and design an Automated Teller Machine System using UML diagrams in the Rational Rose Software. To protect their account form other users to access. Mini Statement. User can simply insert ATM card into the ATM Machine and follow the simple instructions provided by the machine to get the required amount from his/her own account. PROJECT SCOPE: The main scope of the project is to perform the transaction and to update own account balance using an ATM Machine System.EX. WITHDRAWAL: . The pin number or the code number is verified with the database of the customers. password is provided which is called a pin number and is provided uniquely for each user. and Pin Change. Balance. Deposit. VERIFICATION OF ATM CARD: For the verification of ATM card by the System. The transaction options are Withdrawal. It is nothing but immediate aspect of getting money by using simple word. The user can also deposit the amount in their account either by cash/cheque.
DEPOSIT: In this module. after the transaction process is performed by the user. MINI STATEMENT: In this module. the System displays the balance amount available in the account and the amount withdrawn by the user through receipt. BALANCE: In this module. DISPLAY THE RECEIPT: In this module. the user can get a printed statement of his/her account details in the form of hard copy it can be the details of the last 15 days transaction or the entire transaction according to the users wish. The withdrawal amount should be minimum then the current amount in his/her account. . the user can deposit the amount in his/her account in the form of cash/cheque provided and the amount gets transaction to his/her account. The receipt will be provided at the end of the transaction process. PIN CHANGE: In this module. the user can withdraw the required amount from the ATM Machine by inserting his/her card and providing the correct pin number if the pin number does not match with the database then it reject the card.In this module. the user can check his/her Balance provided with the correct pin number if the pin number is wrong then again the ATM machine rejects the card. the user can change the pin number according to his/her wish provided the pin number should be a 4 digit number if the provided pin number matches with the already existing pin number then the ATM machine requests for a different pin number and if the entered pin number is unique then it accepts and from that moment your pin number changes.
info acc.Class Diagram: Money Owner Transaction() Message Sender Receiver Intimation() Status Income Check() Balance Amount Calculation() Receipt name acknow() Log User Verify() Envelope acceptor User name acc.no submit detail() card reader card no acc no validity check() session 1 user detail submit_detail() transaction 1 acc no card no validity() card pan no acc no transac() acct.no name transac() withdraw name transac() deposit acc no card n o transac() enquriy acc no cheque no transaction() Component View: ATM System Use-case Diagram: .no Address Transation() operator panel card no pan no Secured enquiry() Cash Dispenser Acc no Transac() Atm acc no name transac() Receipt print cheque no date transac() custom. console name venue acc.
Session admin user Banking pin Reject Transaction pin change Mini statement Deposit balance enquiry with draw .
Collaboration Diagram: 1: insert card 3: pass word 7: cash 11: saving 15: amount 19: current 23: amount 27: amount 31: recreipt 35: req.pin change 38: enter curr pin 41: enter the new pin 46: no admin Customer 2: enter pin 6: cash withdraw 14: enter the amt 18: continue 22: enter the amt 26: enter the amt atm 30: continue 34: continue 44: pin changed 45: continue 47: take the card 13: verified 17: transaaction process 4: red pass 8: request 10: current 36: req 39: req 42: req 5: verified 9: saving 37: proceed 40: proceed 43: proceed 32: request recreipt recript print 33: reciept processed 20: request transaction 24: request transaction 28: request transaction 12: requset 21: transaction process 16: req transaction 25: transaction process 29: transaction processed current acc saving acc .
Sequence Diagram: Customer insert card atm admin sav acc ing current acc recript print enter pin pass w ord red pass v erified cash w ithdraw cash request sav ing current sav ing requset v erified enter the amt amount req transaction transaaction process continue current request transaction transaction process enter the amt amount request transaction transaction process .
req transaction transaaction process continue current request transaction transaction process enter the amt amount request transaction transaction process enter the amt amount request transaction transaction processed continue recreipt request recreipt reciept processed continue req.pin change req proceed enter curr pin req .
Activity Diagram: Cash Withdraw: Current session Banking Enter pin is pin valid yes cash withdraw no pin invalid saving acc current acc enter the amt enter the amount tranasction process transaction colect cash collect cash .
Balance Enquiry: Atm Machine Enter Pin Pin Checking Invalid pin Balance Enquiry Saving account Current Account Bal checking Check Balance Print Balance Print balance .
Deposit: customer session Baking Enter the pin is pin vaild no pin is invalid deposit enter amt transac amt depocited .
Mini Statement: banking enter the pin is pin valid yes mini statement no invalid pin saving account current account last 15days transac detail print the detail .
Pin change: BANKING enter pin invalid pins yes no invalid code pin change new pin Reenter the pin pin changed .
This will be under the control of telephone operator. DELIVERY REPORT: Delivery report will contain detail about the Stocks delivered to the Customer. The developing process of this System has to take care of certain important stages with the strong view that it deals with the most important instance of the world. Hence lots of efforts are taken to ensure that the administrator i.e. the employer enjoys all the benefits of this System. Updating the performed whenever a new stock is purchased (or) when a stock is delivered. this will be under the control of sales clerk.EX. PROJECT SCOPE: The Stock Maintenance System is developed after the component of the entire necessary UML Component diagram. It also . the currency. with ease and accuracy.e. All these constraints are considered the system is developed to cater to the needs of the industry. UPDATE REPORT: Update Report will contain detail about the recent modification of the stock database. NO: 7 STOCK MAINTENANCE AIM: To design and develop the Stock Maintenance System for processing the Stock details of an industry or organization using Rational Rose Software.. WALK IN SALE: Walk in Sale will contain details about the stocks ordered in person. MODULAR DESCRIPTION: STOCK REPORT: Stock Report will contain all the detail about the stocks purchased quality of stocks and cost details of the stocks. The developed System plays a vital role irrespective of the field of work because it has own importance as it provides complete solution in protecting and managing the stock details of an Industry. which offers higher reliability and efficiency in handling. It must flexible in such a way that it allows future enhancement (or) modification i.. contains detail about the profit and lose encountered during the self of stocks. these enhancement and all other aspects are handled and it is tailored in such a way that it meets the need of the administrator. OBJECTIVE: The main objective behind developing the system is to handle the most important System which has its root in almost all the companies and firms. This System requires utmost care because there should not be any errors in processing as well as managing the Stock details of the industry of a Concern. PHONE ORDER: Phone Order will contain detail about the stocks ordered through Phone.
Class diagram: Delivery report item name : String Quantity : integer report : String get name() get date() get report() Phone Order ordered Item : String Quality item : Integer Available : String Price : integer order() check list() display() Walk in sale Order Item : String Avail item : String Quality : Int price : int Check Item() Display() Purchase_details cust_name : String puchase : string Date of purchase : integer Amount paid : integer Pay bill : int get get get get cust_name() per_item() date() amount() Stock Report avail item : string item name : string price : int check item() display() Update report Solid item : string Avail item : string Quality : int Price : int get get get get sold item() avail item() quality() price() Component View: Stock maintanance .
Deployment Diagram: receipt current customer saving atm system pin change admin transaction .
Use Case Diagram: stock details maintainer update stock report sale purchase details phone order work in sale telephone operator sales clerk .
of item 2: purchase order purchase order 5: maintain stock report stock keeper 4: maintain update report maintain report 3: maintain damage report update report damage report .of item 1: no.Collaboration Diagram: no.
of item no.Sequence Diagram: stock keeper no.of item purchase order damage report update report maintain report purchase order maintain damage report maintain update report maintain stock report .
Activity Diagram: Phone Order: customer name name of available item quality of the available item items purchased date of purchase amount paid .
Purchase Details: name of the item purchased quanitity of the item purchase date and report Sale: customer na list of items solds date of sales amount rec eived pay bills .
Stock Details: name of the available item entry of required items new item arrived yes quantity of the item no price of the item .
Update: item present number of items bought number of item sold sold to stock list reduce from stock list load details and save Walk-In-Sale: item present number of items bought number of item sold sold to stock list reduce from stock list load details and save .
Deployment Diagram: purchase order stock keeper no.of items stock maintenance damage report maintain report damage report .