Touoy Stvoy HELeEe ey Sum Poowa www.ignousite.com Course Code : BCS-051 Course Title: Introduction to Software Engineering Assignment Number : BCA(V)-051/Assign/2020-21 ‘Maximum Marks : 100 Weightage : 25% Last Date of Submission : 31st October, 2020 (For July,2020 Session) 15th April, 2021 (For January,2022 Session) 1. Develop SRS as per IEEE standard for Library Information System. Make assumptions wherever necessary. Ans. 1. Introduction : ‘development process consist of various phases, each phase ending witha defined output. The main reason for having a phased process is that t breaks the problem of developing software into successfully performing a set of phases, each handling a afferent concern of software development. This ensures that the cost of development is lower than what it would have been if the whole problem was tackled together. Furthermore; phased process allows proper checking for quality and progress at some defined points during the development (end of process). Without this one would have to wait untilthe end to see what software has been produced Any problem Solving in software consist ofthese steps:~ © Requirement Analysis + Requirement Analysis is done in order to understand the problem the software system is to solve. There are two major activities in this phase: problemunderstanding or analysis and requirement specification. In problem analysis, the aim is to understand the problem and its context, and the requirements of the new system that is to be developed. Once the problem is analyzed and the essentials understood, the requirements must be specified in the requirement specification document. The requirements document must specify all functional and performance requirements; the formats of inputs and outputs etc + Software Design : The purpose of design phase is to plan a solution of the problem Specified by the requirements dacument. This phase is the first step in moving from the problem domain to solution domain, The design activity often results in three separate outputs: architecture design, high level design and detailed design. © Coding : The main goal of coding phase is to translate the design of the System into code in a given programming language. The coding phase affects both testing and maintenance profoundly. The goal of coding should be to reduce the testing and maintenance effort, hence during coding the focus should be on developing programs that are easy to read and understand. © Testing The function of testing is to detect the defects in the Software, The main goal testing is to uncover requirement, design and coding errors in the programs. Ignou Study helper-Sunil Poonia Page 1Touoy Stvoy HELeEe ey SUNIL POONA ‘The main goal of the requirement phase is to produce the software requirement specification (SRS), which accurately capture the client's requirements. SRS is A document that describes what the software should do, The basic purpose of SRS Is to bridge the communication gap between the clients, the end users and the Software developers. Another purpose is helping user to understand their own needs, www.ignousite.com 1.1 Purpose: The SRS typically contains the brief description of the project. The purpose of the requirement document is to specify all the information required to design, develop and test the software. ‘* The purpose of this project isto provide a friendly environment to maintain the details of books and library members, ‘¢ The main purpose of this project is to maintain easy circulation system using computers and to provide different reports. 1.2 Scope: ‘The document only covers the requirements specifications for the Library Information Systern. This document does not provide any references to the other component of the Library information System. All the external interfacesand the dependencies are also identified in this document. Feasibility study: The overall scope of the feasibility study was to provide sufficient information to allow a decision to be ‘made as to whether the Library Information System project should proceed and ifso, its relative priority in the context of other existing Library Management Technology. The feasibility study phase of this project had undergone through various steps which as describe as under: ‘+ Identity the origin the information at different level ‘© Identity the expectation of user from computerized system, ‘* Analyze the drawback of existing system(manual system) 1.3 Definition, Acronyms, Abbreviation: ‘* JAVA > platform independence © SQL > Structured query Language ‘© DFD ->Data Flow Diagram, © CFD > Context Flow Diagram © ER > Entity Relationship ‘© IDE > Integrated Development Environment. © SRS -> Software Requirement Specification 1.4 Reference: ‘© An integrated Approach Software Engineering Third Edition by Sunil Poonia, Ignou Study helper-Sunil Poonia Page 2Touoy Stvoy Heuree e Sum. Poo www.ignousite.com ‘© Java: Balaguru swamy © SQL Josepht Jorden 1.5 Overview: ‘The implementation of Library Management starts with entering and updating master records like book details, library information, Any further transaction like book issue, book return will automatically update the current books 2. Overall Description : 2.1 Product Perspective: The proposed Library Information System will take care of the current book detall at any point of time. The book Issue, book return will update the current book details automatically so that user will get the update current book detail. 2.2 Product functio ‘© The main purpose of this project is to reduce the manual work. ‘¢ This software is capable of managing Book Issues, Returns, and Calculating/Managing Fine. Generating various Reports for Record-Keeping according to end user requirements 2.3 User characteristics: We have 2 levels of users ‘+ User module: In the user module, user will check the availability of the books. + Book return ‘= Administration module: The following are the sub module'in the administration module, + Register user + Entry book details © Bookissue 2.4 General Constraints: ‘Any update regarding the book from the library is to be recorded to have update & correct values. 2.5 Assumption and dependencies: All the data entered will be correct and up to date. This software package is developed using java as front end which is supported by sun micro system. Microsoft SQL server 2005 as the back end which is supported by Window 7, 3, Specific Requirement: 3.1 External Interface Requirement: The user should be simple and easy to understand and use. Also be an interactive interface .The system should prompt for the user and administrator to login to the application and for proper input criteria Ignou Study helper-Sunil Poonia Page 3Touoy Stvoy HELeEe ey SUNIL POONA www.ignousite.com 3.1.1 User Interface: ‘The software provides good graphical interface for the user any administrator can operate on the system, performing the required task such as create, update, viewing the details of the book. + Allows user to view quick reports like Book Issues/Returned etc in between particular time. ‘+ Stock verification and search facility based on different criteria, 3.1.2 Hardware interface: ‘© Operating system : window © Hard disk :40 GB. © RAM: 256 MB. + Processor : Pentium(R)Dual-core CPU Software interface : = Java language © Net beans IDE 7.0.1 = MSSQL server 2005, 3.1.4 Communication interfac Window 3.2 Functional requirements: ‘= Book entry: In this module we can store the details of the books. ‘= Register student: in this module we can keep the details of the new student. ‘= Book issue: This module is used to keep a track of book issue detail. = Book return: This module enables to keep a track of return the books. 3.3 Performance requirements: ‘The capability of the computer depends on the performance of the software. The software can take any number of inputs provided the database size is larger enough. This would depend on the available memory space. Design constraints : Each member will be having a identity card Which can be used for the library book issue, fine payment etc, whenever library member wish to take a book, the book issued by the library authority will be check both the book details as well as, the student details and store it in library database. in case of retrieval of book much of human intervention can be eliminated. System attributes : Ignou Study helper-Sunil Poonia Page 4Touoy Stvoy Heuree e Sum. Poo ‘= Maintainability: There will be no maintained requirement for the software. The database is provided by the end user and therefore is maintained by this user. + Portability: The system is developed for secured purpose, soit is can’t be portable, ‘= Availability: This system will available only until the system on which itis instal, is running. ‘Scalability: Applicable, www.ignousite.com 3.6 Other requirements: There are no other requirements, Q2. Develop Design Document for the System mentioned in Question no.1 Ans. 1. Introduction: Detailed design starts after the system phase and system has been certified through the review. The goal of this phase is to develop internal logic of each of the modules identified during system design In the system design, the focus is an identifying the modules, whereas during the detailed design the focus is on designing the logic for the modules. In other words in system design attention is on what components are needed, while in the detailed design how the component can bé implemented in the software isthe issue. The design process for software system has two events. At the first level focus is on deciding which modules are needed for the system, the specification of these modules and how the modules should be interconnected. This is called system design or top level design. In the specification of the module can be satisfied is decided. This design level is often called detailed design or logic design, because the detailed design is extension of system design, system design controls the major structural characteristics of the system. The system design has a major impact testability and modifiability of a system and Impacts its efficiency much of the design efforts for the designing software are spent creating the system design. 2. Applicable documents: ‘The detailed design refers the system documents hence the first application documents here is system design, also we are referring the data structure. Hence second application document here is database design 3, Structure of software package: The software package consists of following functional components. ‘= Functional component 1: Registration. + Functional component 2: Book issue. ‘© Functional component 3: Book return. ‘+ Functional component 4: Search/view book details. ‘© Functional component S: Update book details. ‘+ Functional component 6: Payment (Fine). Ignou Study helper-Sunil Poonia Page 5Touoy Stvpy HELPee e Sum. Poo www.ignousite.com 31 Structure charts: Its graphics representation of the control logic of processing function or module representation of the system. itis one of the most common methods used for system design. n a structure charts each program module is represented by a rectangle box, modules at the top level of the structure charts call the modules at the lower level. The connection between modular are represented by lines between the rectangular boxes. The connection describes the data flows between the called and calling modules. 4, Module Decomposition: 4.1 Student details: In this form the users have to enter the details about the student like name, regno, course..etc. If the proper details are not entered at the same time error message will be displayed and record will not be stored...And if the entered register number is already exist then the details can't be stored and error message will be displayed. 4.2 Delete student deta In this case admin can delete individual student details by entering his register number .If the Register no is not entered at same time message will be displayed and record will not be Stored...And if the entered number is already deleted then it will be giving the message, 33 Book issue: In this form the Liberian can issue the boOks to the student. If the books are already distributed to students then Liberian can’t issue those particular books. 4.4 Book return: Here the user must return the book on given date... Otherwise fine will be calculated. 45 Calculate fine: In this case we can maintain the late fine of library member who return the issued book after the due date... Database Name: bookdetails Field Name Data Type Size Relation ‘ACen Varchar 50 Primary Key ‘author Varchar 50 Not null Title Varchar 50 Not null Publication Varchar 50 Not null Edition Varchar 50 Not null No_of copies int Not null Volume Varchar 30 Not null Date_pur Varchar 30 Not null Ignou Study helper-Sunil Poonia Page 6fs Touou Sry HeLa Sumi. Poona Price Decimal 8.2) Not null Status ‘Varchar(50) 50 Not null Database Name: student Field Name Datatype | Size Relation Name Varchar 50 Not null Regno Varchar 50 Primary key Date_of issue Datetime Not null Aadresss Varchar 50 Not null Date_of return Datetime Not null Course Varchar 50 Not null ‘Accno Varchar 50 Foreign key Gender Varchar 50 Not null Database Name: issue Field Name Data Type ‘Size Relation Regno Varchar 50 Foreign key Date_of_issue_books Datetime Not null Date_of_return_books Datetime Not null ‘Accno Varchar 30 Not Null Name Varchar 50 Not null Course Varchar 50 Not null ‘Author Varchar 50 Not null Volumn Varchar 50 Not null Edition Varchar 30 Not null Database Name: return Field Name Datatype | size Relation Rego Varchar 50 Foreign key ‘Accno Varchar 50 Not Null Date_of_return_books Datetime Not null Date_of_lssue_books Datetime Not null Name Varchar 50 Not null Course Varchar 50 Not null ‘Author Varchar 50 Not null Ignou Study helper-Sunil Poonia Page 7Touoy Stvoy Heuree Se Sum. Poo www.ignousite.com Voluman Varchar 50 Not null Edition Varchar 30 Nat null 5 Entity Relationship Diagram: Entity Relationship Diagram is used in modern database software engineering to illustrate logical structure of database. It is 2 relational schema database modeling method used to Model a system and approach. This approach commonly used in database design. The diagram created using this method is. called ER-diagram, The ER-diagram depicts the various relationships among entities, considering each object as entity. Entity is represented {as rectangle shape and relationship represented as diamond shape. It depicts the relationship between data object. The ER- diagram is the notation that is used to conduct the data modeling activity. Entity: Entity is the things which we want to store information. it is an elementary basic building block of storing information about business process. An entity represents an object defined within the information system about which you want to store information. Entities are distinct things in the enterprise. Relationship: A relationship is normal connection or association between entities used to relate two or more entities with some common attributes or meaningful interaction between the object: Attributes: Attributes are the properties of the entities and relationship descriptor of the entity. Attributes are elementary pieces of information attached to an entity. @QPs 0 G99 @ ER-Diagram Library Information System Ignou Study helper-Sunil Poonia Page 8Epa rr Sumi. Poona www.ignousite.com 6 DFD diagram Library Information System: | Book shelves | Book request ‘Student ti of thors | Lista ites List of epee Book request Search by tk Tose on opi Topic io Level 1 DFD — Tease aks “hae amb sod bakin — stars 5 et Find Sook Position a Uist of ites Bok title Updated list of borrowed Level 2 DFD Ignou Study helper-Sunil Poonia Page 9Touoy Stvoy Heuree e Sum. Poo www.ignousite.com 7 interface Design The purpose of interface design is to determine how the layout of the system and to make sure that this layout suitable with user requirement. The good designing can attract the users and supposedly not confused the users with each functions of the system. For instance, the developer also needs to concern about userfriendly interface during designing phase. Through this system, there are some elements, which been used to design the interface. Interface may Contain following controls: 7.1 Text Box The user can key in the input in the text boxes. However, certain text boxes only receive numeric inputs, but not character input such as Name, 7.2 Button There are a few buttons which been prepared for the user's usage such as accept, ok , cancel,close, update, save , print and search button, All these buttons have thelr own functions. 7.3. Combo Box The purpose Of the combo box isto list all selection items there. Therefore, the users do not need to Key in any input, but they can drag down the scroll and choose the best lst as their input. A Data Designer Report Generator It used to view the repart about summary of data record alist of files, which are already kept in database, 8 Prototype Design : A prototype is a visible, mini replica of the real system that has essential function and important interfaces, but not the whole system itself. The idea is to build.a:first simplified version of the system and seek feedback from the p eople involved in order to then design a better version: This process is repeated until the system meets the client’s condition of acceptance. Q3. What Change Management? Explain the process of changing requirements for a Software to be developed. Ans. Change Management: Change management isthe discipline that guides how we prepare, equip and support individuals to successfully adopt change in order to drive organizational success and outcomes. ‘While all changes are unique and all individuals are unique, decades of research shows there afe actions we can take to influence people in their individual transitions. Change management provides a structured approach for supporting the individuals in your organization to move from their own current states to their own future states. Three Levels of Change Management 1L individual Change Management While itis the natural psychological and physiological reaction of humans to resist change, we are actually quite resilient creatures. When supported through times of change, we can be wonderfully adaptive and successful. Individual change management requires understanding how people experience change and what they need to change successfully, It also requires knowing what will help people make a successful transition: what messages do people need to hear when and from whom, when the optimal time to teach someone a new skill is, how to coach people to demonstrate Ignou Study helper-Sunil Poonia Page 10Touoy Stvoy Heuree e Sum. Poo ‘new behaviors, and what makes changes “stick” in someone's work. Individual change management draws on disciplines like psychology and neuroscience to apply actionable frameworks to individual change. After years of studying how individuals experience and are influenced in times of change, Prosci developed the ADKAR Model for individual change. Today, itis one of the most widely used change models in the world. www.ignousite.com 2.Organizational/Initiative Change Management. While change happens at the individual level, itis often impossible for a project team to manage change on a person-by- person basis. Organizational or initiative change management provides us with the steps and actions to take at the project level to support the hundreds or thousands of individuals who are impacted by a project. Organizational change management involves first identifying the groups and people who will need to change as the result of the project, and in what ways they will need to change. Organizational change management then involves creating a customized plan for ensuring impacted employees receive the awareness, leadership, coaching, and training they need in ‘order to change successfully. Driving successful individual transitions should be the central focus of the activities in ‘organizational change management. Organizational change management is complementary to your project management. Project management ensures your project's solution is designed, developed and delivered, while change management ensures your project’ solution is effectively embraced, adopted and used. Learn more about the Prosci 3-Phase Process, which provides ifesearch-based approach and full set of tools for applying. change management at the initiative level 3.Enterprise Change Management Capability Enterprise change management is an organizational core competency that provides competitive differentiation and the ability to effectively adapt to the ever-changing world. An enterprise change management capability means effective change ‘management is embedded into your organization's'roles, structures, processes, projects and leadership competencies. Change management processes are consistently and effectively applied to initiatives, leaders have the skills to guide their ‘teams through change, and employees know what to ask for in order to be successful. The end result of an enterprise change management capability is that individuals embrace change more quickly and effectively, and organizations are able to respond quickly to market changes, embrace strategic initiatives, and adopt new technology more quickly and with less productivity impact. This capability does not happen by chance, however, and requires a strategic approach to embed change management across an organization. Process of changing requirements for a Software: Changing software requirements is a normin project development. Today, businesses are trying to keep up with the high «dynamics in the markets, technology and trends and expect the same attitude from technology vendors and partners. To keep the product up-to-date, our clients may rethink their ideas, modify their concepts, shift priorities. They often add or bale on product features to better address customer needs and adjust to the ever-changing business space and market conditions. In other words, the changes in project requirements are inevitable. We accept it and know how to deal with changing requirements on different projects. Also, we realize the importance of effective management in this environment, ‘Why managing project requirements is important? Ignou Study helper-Sunil Poonia Page 11Touoy Stvoy Heuree e Sum. Poo Effective management of changing project requirements is essential for leading a product to a successful launch on time and. within budget. Poor management, on the contrary, implies sufficient risks and losses: www.ignousite.com ‘= delays or a complete failure to meet important project deadlines, exceeded budget, ‘© misunderstanding within teams and between a client and a vendor, ‘© lack of control over the project development. In order to avoid these risks, both clients and vendors should understand the importance of changing project requirements management and adopt reliable techniques to ensure its efficiency. And here come two issues: LOften, clients don’t realize how serious the changes they offer are and what it takes to implement them. This confusion ‘emerges for different reasons, For example, stakeholders may lack the expertise to understand the technology and complexity behind the system and its functionality. In other cases, clients don’t follow the course of the project and may suggest modifying the key feature that in turn triggers the need to change many other features or reconfigure the whole system 2.When changing requirements appear at the final stages of product development, they are usually harder to manage and implement and call for more critical analysis. In many cases, these changes may cause significant delays in delivery and cost increase. In my practice, both these issues and the causes of poor changing requirements management can be tackled or even avoided with the help of proper communication, The best strategy for a service provider to overcome the first issue is to provide detailed estimations and hold explaining or ‘educational sessions for a client. Do not just throw numbers at your clients. Let them understand how changes they request affect the system and why. The second issue is harder to resolve. You have to constantly keep the decision makers on the client's side aware of the project development status, show the dependency between front-end and back-end functionality and project development stages when there's stil room for making changes. Now let's discuss how to deal with chanige requests on fixed-price and time and material projects Ignou Study helper-Sunil Poonia Page 12