Software Development Lifecycles, Assignments of Computer science

Download Software Development Lifecycles and more Assignments Computer science in PDF only on Docsity!

BTEC Higher

National

Diploma in

Computing

Unit 09 : Software Development

Lifecycles

Computing STUDENT ASSESSMENT SUBMISSION AND DECLARATION

Assessor name :

Issue date: Submission date: Submitted on:

Program:

BTEC Higher National Diploma in Computing

Unit:

Unit 09 : Software Development Lifecycles

Assignment number and title:

Assignment 03 - Software Development Lifecycles

Computing Unit 6 Assignment Brief Student Name & Student ID: Unit Number and Title: Unit 09 : Software Development Lifecycles Academic Year: Unit Assessor:. Assignment Title:

Assignment 03 - Software Development Lifecycles

Issue Date: Submission Date: Internal Verifier Name: Date:

Computing Task 01

Chapter 01 : Introduction

1.1. Purpose As all other projects, this project has its objectives that are being followed as it is being developed.  To handle all primary information required to calculate monthly statements. Separate database is maintained to handle all the details required for correct statement calculation and generation.  To introduce more user friendliness in the various activities such as record updating and maintenance.  Similarly, record maintenance and updating can also be accomplished by using the identification of the customer with all details being automatically generated. These details are also being promptly automatically updated in the master file thus keeping the record absolutely up to date.  The system has maintained in the database or files and however wants to retrieve can’t retrieve unless authorized.  More security  For publicity purposes  Less time consuming  Proper database  Easy to use(user interface)  Work transforms from manual to automatic  Feedback 1.2. Scope Library management system ensures the effective use of the texts books that will be available in the book store. This management can be able to record a number of texts books in the data base. Unlike the file system. Where by the details were used to be stored in files. And they could succumb to some problems give like the termite, fire hazards, and rats, among others. This can store any number of data because its storage is unlimited. 1.3. Problem statements This study will support and manage library transactions and services in Londontec city Campus. Also, the computer technology students will be able to develop software for a design of library monitoring system in response to the problems in the current manual library operations, services and transactions are enumerated below:

Computing Using the techniques which are mentioned above, we can collect data conveniently and proceed with our project.

3.1 Introduction

In order to present clear information on the process of software development to the developers, we divide the process into categories. It will be presented to the developers using the models. Using methodology is useful to present a clear idea to any of the members in this development process. Here, Diagrams and flow charts are used to present the process of software development concisely.

3.2 Entity Relation Diagram

member book member no name phone email address borrow checkout_date borrow_period ISBN book _ title authors

Computing

3.3 Flow Chart

Computing Task 02

The two ways Improve software quality

 Importance of data collecting techniques

Using the collected data, we can perform better in the decision-making process. So that the developers will be able to develop a user-friendly system to manage the library. And we can identify possible problems which can happen in the future by using the collected data. So, we can either find a solution beforehand to fix it or find ways to prevent the possible problems. Also, we can identify and categorize necessary and unnecessary features using the collected data and apply the most important features to the software.

 Importance of diagrams and flowcharts

By studying diagrams and flowcharts, we can study the whole process of software development. After that, we can add functionalities to the system to improve the system. Also, we can identify inefficiencies of the system and apply solutions. And the diagrams & flowcharts will help readers to study this complex structure easily. By using diagrams and flowcharts, we can easily define data & present a clear idea. And it provides convenience when studying the structure of the software. Also, diagrams & flowcharts make it easy to explain the process quickly to the users. Also, they provide a system-related summary. As the mentioned facts in this paragraph, it is clear that the given data collection techniques help in improving the overall quality of the library management system. Task 03 3 - Function Design

3.1 Flowcharts

Function designs can improve the quality of software significantly. It applies to this library management system too. Here we discuss flowcharts and data flow diagrams. The flow chart can be defined as an important tool to improve the wide variety of processes. By using a graphical presence, we can help project teams to identify different elements of the software development process and the interrelationships among the steps of the software development process. Here we have used flowcharts to improve communication within the Project team. So those members of the project team can collaborate as they create, edit and analyze flowcharts. Also, it helps developers to follow the production workflow as it is easier when it is in a visual format.

Computing Using the flowcharts, we improved the visual clarity of the software development lifecycle. It helps to bring clarity to concepts that are difficult to understand. It helps people to navigate complicated, interrelated systems without wasting time and identity the points of interest at a glance. Also, the flowcharts make the analysis easier as they have different elements to denote different actions. As we have equipped with the right flowchart program, we could quickly create visual representations of the elaborate systems. So that people would be able to easily explore and understand the processes, interactions, and sequences. To achieve effective analysis flowcharts are used. Flowcharts help us/developers to visually identify problems. They highlight operational bottlenecks and areas for improvement. By visually reviewing the flowcharts, developers can identity illogical sequences which can create bugs and inefficiencies. After identifying a potential problem, developers can identify in which places they need to modify their codes. By creating a visual representation of a problem and its possible solutions, we can understand it better. By inviting collaboration, other developers can contribute to the diagram so we can get a comprehensive view of the problem. And we will have a chance to find a better solution by working together on analyzing the issue. Using the flowcharts, we can break down a problem into well-defined parts while solving the problem. Flowcharts can help developers to make sure whether we have or haven’t included all available information that pertains to the matter. For the most part, we can see whether we have omitted from our consideration any essential inputs, operations, or decisions. We have used flowcharts to simplify the difficult procedures. By creating user-facing documentation for the library management system in flowchart form we can help Library Staff learn to properly use Library Management System. Users may feel more satisfied with the final product. Using flowcharts, we can present a big picture of our library management system. We can provide a clear idea of the process such as the use of data, use of the functionalities, output information &, etc.

3.2 Data Flow Diagram

The data flow diagram (DFD) maps out the information/data for the system. Creating a data flow diagram will help the developer to create a system with less discomfort in developing the actual code and increase the productivity of the developers further. And the most important thing about a data flow diagram is it keeps the program organized. We have used the data flow diagram to plan on how the Library Management System is going to achieve its intended purpose. Also, it helps us to keep the system on track.

Computing Last but not least, we have the Evaluation phase. When using the software, users require more requirements time to time. So, the developers get to identify new requirements and update the software according to the users’ requirements. Task 05

A Library Management System is a software built to handle the primary housekeeping functions

of a library. Libraries rely on library management systems to manage asset collections as well as

relationships with their members. Library management systems help libraries keep track of the

books and their checkouts, as well as members’ subscriptions and profiles.

Library management systems also involve maintaining the database for entering new books and

recording books that have been borrowed with their respective due dates.

System Requirements

We will focus on the following set of requirements while designing the Library Management System:

1. Any library member should be able to search books by their title, author, subject category as well by the publication date.
2. Each book will have a unique identification number and other details including a rack number which will help to physically locate the book.
3. There could be more than one copy of a book, and library members should be able to check-out and reserve any copy. We will call each copy of a book, a book item.
4. The system should be able to retrieve information like who took a particular book or what are the books checked-out by a specific library member.
5. There should be a maximum limit (5) on how many books a member can check-out.
6. There should be a maximum limit (10) on how many days a member can keep a book.
7. The system should be able to collect fines for books returned after the due date.
8. Members should be able to reserve books that are not currently available.
9. The system should be able to send notifications whenever the reserved books become available, as well as when the book is not returned within the due date.

Computing

10. Each book and member card will have a unique barcode. The system will be able to read barcodes from books and members’ library cards.

Use case diagram

We have three main actors in our system:  Librarian: Mainly responsible for adding and modifying books, book items, and users. The Librarian can also issue, reserve, and return book items.  Member: All members can search the catalog, as well as check-out, reserve, renew, and return a book.  System: Mainly responsible for sending notifications for overdue books, canceled reservations, etc. Here are the top use cases of the Library Management System:  Add/Remove/Edit book: To add, remove or modify a book or book item.  Search catalog: To search books by title, author, subject or publication date.  Register new account/cancel membership: To add a new member or cancel the membership of an existing member.  Check-out book: To borrow a book from the library.  Reserve book: To reserve a book which is not currently available.  Renew a book: To reborrow an already checked-out book.  Return a book: To return a book to the library which was issued to a member.

We have three main actors in our system:

 Librarian: Mainly responsible for adding and modifying books, book items, and users.

The Librarian can also issue, reserve, and return book items.

 Member: All members can search the catalog, as well as check-out, reserve, renew, and

return a book.

 System: Mainly responsible for sending notifications for overdue books, canceled

reservations, etc.

Here are the top use cases of the Library Management System:

 Add/Remove/Edit book: To add, remove or modify a book or book item.

 Search catalog: To search books by title, author, subject or publication date.

 Register new account/cancel membership: To add a new member or cancel the

membership of an existing member.

 Check-out book: To borrow a book from the library.

 Reserve book: To reserve a book which is not currently available.

 Renew a book: To reborrow an already checked-out book.

 Return a book: To return a book to the library which was issued to a member.

Computing

Computing

Class diagram

Here are the main classes of our Library Management System:  Library: The central part of the organization for which this software has been designed. It has attributes like ‘Name’ to distinguish it from any other libraries and ‘Address’ to describe its location.  Book: The basic building block of the system. Every book will have ISBN, Title, Subject, Publishers, etc.  BookItem: Any book can have multiple copies, each copy will be considered a book item in our system. Each book item will have a unique barcode.  Account: We will have two types of accounts in the system, one will be a general member, and the other will be a librarian.  LibraryCard: Each library user will be issued a library card, which will be used to identify users while issuing or returning books.  BookReservation: Responsible for managing reservations against book items.  BookLending: Manage the checking-out of book items.  Catalog: Catalogs contain list of books sorted on certain criteria. Our system will support searching through four catalogs: Title, Author, Subject, and Publish-date.  Fine: This class will be responsible for calculating and collecting fines from library members.  Author: This class will encapsulate a book author.  Rack: Books will be placed on racks. Each rack will be identified by a rack number and will have a location identifier to describe the physical location of the rack in the library.  Notification: This class will take care of sending notifications to library members.

Computing

Activity diagrams

Check-out a book: Any library member or librarian can perform this activity. Here are the set of steps to check-out a book:

Computing