A software for wedding planner, Study Guides, Projects, Research of Computer science

Download A software for wedding planner and more Study Guides, Projects, Research Computer science in PDF only on Docsity! Wedding Planner Software Engineering Project Report (C-IX) Submitted by: Supervisor: Jatin (7849) Anshu(7807) Aryan(7843) Nikita(7737) Dr. Anjali Thukral 2020 Department of Computer Science Keshav Mahavidyalaya University of Delhi ACKNOWLEDGEMENT We would like to thank our Principal "​Mrs Madhu Pruthi ​" and especially our S.E. teacher "​Mrs Anjali Thukral Mam " whose valuable guidance has been the one that helped us patch this project and make it full proof success. Her suggestions and her instructions have served as the major contributor towards the completion of the project . Then we would like to thank our Parents and friends who have helped us with their valuable suggestions and guidance which has been fruitful in various phases of the completion of the project. Last but not the least we personally thank each other for wonderful cooperation,ideas and fun company to work and learn with . Other Non-functional requirements 13 Performance requirement 13 Safety and Security requirement 13 Data flow Diagrams 13 Level 0 13 Level 1 13 Level 2 13 Data dictionary 13 Project Management 13 Estimations 13 Function Points 13 Efforts and Cost 13 Scheduling 13 Risk Management 13 Design Engineering 13 Architectural Design 13 Data Design 13 Coding 14 Testing 14 References 14 Problem Statement A Wedding planning system has a major focus on organising the bridal in the best and synchronised and efficient way. Manually operating such a big get together leads to utter chaos, heated arguments, missing out things, running out of time and an overhead needed to adapt to sudden change in plan. Due to the presence of these drawbacks there is a need for a WPS(Wedding planning system). A Wedding planning software is being designed for professional wedding planners and their customers. This software will be operated on a website and an android application. The major inputs for the software will be from the users and the planners. The user will be allowed to input theirp personal details and the important information regarding events, whereas planners will be able to post the photos and videos of the previous work including maintaining different to-do’s and lists needed for the wedding. The data which is required to maintain from the user end will be the personal details and other information regarding events like lists of guests whereas from the planners end will be the lists, feedback and associates. The important modules which will be included are User registration, Previous work glimpses, Meeting and Contacts, Invitations, and initrary generation . The major outputs of the software will be the itinerary of the wedding events for the planner, and the details of the order. The software enables simultaneous registrations by allowing multiple users to access the wedding website. It allows people/customers to use this service at any time, and also eliminates the need of repeated physical presence. WPS is a benefaction not only for the customer but also for the planners. Process Model The process model we will use is the ​Prototype model​. The basic idea in this model is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is developed based on the currently known requirements. By using this prototype, the client can get an “actual feel” of the system, since the interactions with the prototype can enable the client to better understand the requirements of the desired system. Prototyping is an attractive idea for complicated and large systems for which there is no manual process or existing system to help determine the requirements. The prototype are usually not complete systems and many of the details are not built in the prototype. The goal is to provide a system with overall functionality. Diagram of prototype model planner, who are involved in a wedding. 3. INVOICE TRACKING This module helps the wedding planner track leads in the funnel; create and send customized contracts, proposals and invoices. 1.1.3. User Characteristics To use the system users should have : 1. Command over English Language. 2. A basic knowledge of computers and the Internet. 1.1.4. General Constraints ● Only Admin has right to access database ● Database is not accessible to every user. ● User interface is only in English. No other language option is available. ● An internet connection is required to use the system. A broadband or faster connection is recommended. ● The files in which the information regarding accounts should be secured against malicious deformations. ● Data should not become corrupted in case of system crash or power failure. 1.1.5. Assumption and Dependencies ● Admin is created in the system already. ● Roles and tasks are predefined. ● There is no limit for registering for the website. If this were so then the instantaneous communication between the two systems would not exist. ● In general it has been assumed that the user has complete knowledge of the system that means user is not a naïve user. Any data entered by him/her will be valid. ● It depends that one should follow the international standards for generating the User ID & should fill the related information in the proper format. ● Central server of the system must be able to handle all the incoming requests simultaneously. ● Back up of the databases in case of hardware failure, disaster, natural calamities. ● No data loss in case of handling of the system by admin ● Username are valid email addresses of respective user. ● Administrator has the authority to cancel any registration and request . 1.2. External Interface requirement 1.2.1. User Interfaces ● It is a viewing page, where visitors will see the weddings videos and photos. Then users who are involved in the wedding can login using the login window with Id and password provided. ● Users can select the theme and budget for the wedding first. ● If users don't exist, then the user must register in order to access the system functionality. Id and password will be stored in the database for future login purposes. ● Users logins to select and give suggestions for the items involved in the wedding. ● Wedding planners logins to view ongoing weddings and can select a particular wedding and work on it. 1.2.2. Hardware Interfaces ● The application must run over the internet, all hardware required to connect the system shall be the hardware interface. ● Minimum 1 GB RAM. ● 30 GB hard disk for storage. 1.2.3. Software Interfaces ● Windows operating system or android operating system. ● Web browser. ● WAMP Server. ● MySQL DBMS. 1.3. Functional Requirements 1.3.1. Planning and collaboration This function allows users and wedding planners to plan the basic layout of the wedding. Wedding planners should be able to create a to-do list, guest lists. Users should be able to check out the progress, booking and provide necessary suggestions. 1.3.2. Testimonial Wedding planners should handle the various testimonials received of the previous wedding and this function enables this to be displayed on the 2. Project Management 2.1. Estimations 2.1.1. Function Points S. No Point Grade Value 1. Does the system require reliable backup and recovery? 2 2. Are specialized data communications required to transfer information to or from the application? 3 3. Are there distributed processing functions? 1 4. Is performance critical? 4 5. Will the system run in an existing, heavily utilized operational environment? 5 6. Does the system require on-line data entry? 5 7. Does the on-line data entry require the input transaction to be built over multiple screens or operation? 3 8. Are the ILFs updated online? 2 9. Are the inputs, outputs, files or inquiries complex? 1 10. Is the internal processing complex? 3 11. Is the code designed to be reusable? 4 12. Are conversions and installations included in the design? 0 13. Is the system designed for multiple installations in different organizations? 0 14. Is the application design to facilitate change and for ease of use by the user? 4 Value adjustment factor​, Σf​i ​ = 37 Information domain value Weighing factor Result Simple Average Complex Simple Average Complex External Inputs 7 1 2 3 4 6 37 External Outputs 3 0 1 4 5 7 19 External Inquiries 4 0 0 3 4 6 12 Internal logical files 3 0 0 7 10 15 21 External interface files 3 0 0 5 7 10 15 count total = 104 FP = count total * (0.65 + 0.01 * Σf​i ​) FP = 104 * (0.65 + 0.01 * 37) FP = 104 * (1.02) FP = 106.08 2.1.2. Efforts and Cost The average productivity for this kind of project = 6.5 FP / pm. Total efforts = FP / average productivity = 106.08 / 6.5 = ​16.32 person months Considering the labour rate = $ 8000 Total cost = total effort * labor cost = 16.32 * 8000 = ​$ 1,30,560 2.2. Scheduling PROJECT WEEK: DATE: Identify customer requirements Meet wih concerned errs Identy reeds ane projext cconatsinte -Heanisn prose statement sat FEB man apr. May 7235 4667 S8€90nN BDH 6 Tw 7unwm 24unes swwunlr ~ nw 5 2 cefinee Requirement analysis “Detailed discussion cf the proiea Crete DFD Create Data ictionary Niessen SR specited Project management Rik Table Mieetone :Tialre designed ane coat etinted Timeline constuction ~Aechitecural Seige Design Engineering Date desion talesore System cesion dereoned Pesudo code i Develop Tow graph Testing “Calculate eyctomerti comply Project end