MCSL 217 PRACTICAL SOLUTIONS

  Sessions 19 and 20: Assume that you interested in developing a “Library Information System (LIS)”. Visit any Library.  As a visitor of Library, make a list of requirements that need to be fulfilled by LIS. Now, develop  Software for LIS. Ensure yourself that LIS developed by you is fulfilling the requirements. Preferably,  try to obtain requirements for LIS from any person who visits a library, develop LIS and then get it  Software Engineering Lab validated by him/her. Library Management System This software project is a library management software system with all the basic as well as some innovative features for managing a library. It consists of a large database of various books available in the library. It also lists various books issued to respective readers. The system keeps track of all the books readily available and also the books that have been issued to various readers for the time period for which the books have been issued. The system also handle...

Sessions 17 and 18: Have a look at the output of any program that was not written by you. Preferably, look at an application that is not developed by you and write the program for the development of that application or a portion of that application.  #Calculator     def add(n1, n2):       return n1 + n2;     def subtract(n1, n2):       return n1 - n2;       def multiply(n1, n2):       return n1 * n2;       def divide(n1, n2):       return n1 / n2;       operations = {       "+": add,       "-": subtract,       "*": multiply,       "/": divide            }       num1 = int(input("What's the first number?: "));     for symbol in operations:;       print(symbol);     op...

  Session 16: Select a small portion of any program written by you. Check if the portion of code selected by you is having constructs that violate the structured programming paradigm. If yes, then  rewrite the code to conform to structured programming paradigm. If no, check another  portion of code.  Structured Programming Paradigm Structured programming is a programming paradigm aimed at improving the clarity, quality, and development time of a computer program by making extensive use of the structured control flow constructs of selection (if/then/else) and repetition (while and for), block structures, and subroutines. Popular Programming Paradigms: Imperative Programming Procedural Programming Functional Programming Declarative Programming Object-Oriented Programming Our imperative code: const nums = [1,4,3,6,7,8,9,2]; const result = []; for (let i = 0; i < nums.length; i++) {     if (n...

  Session 15: Select a software that you use regularly such as MS-office, Gmail, MS-Excel etc.   Create a set of usage scenarios for the software.  Usage Scenario of GMAIL  A  usage scenario  (US) is a step-by-step description of one way in which an intervention might be used. The US describes the steps that an external agent might take to achieve a goal using it; they represent how a product is  intended  to be used. Initialization. This involves all the steps needed to get a product ready for use. Use. This involves the steps executed to actually use the product. Finalization. This involves all the steps needed to clean/store/put-away the product. Here, I will describe you about the Google Email called Gmail usage scenario. The software we use regularly i.e., everyday.  Gmail is a free email service provided by Google. In many ways, Gmail is like any other email service: You can ...

  Session 14: Demonstrate the Software developed in Session 13 to any other person and make a list of Changes suggested by him/her. Implement changes in Software following the Change   Control process and demonstrate the updated Software to the same person.    List of changes required to be done:- Confirm reservation for conform seat.  Reservation against cancellation. Waiting list reservation.  Online reservation.  Tatkal reservation.  Lack of security of Data. More man power. Time consuming.  Consumes large volume of pare work  Needs manual calculations.  No direct role for the higher officials. Existing railway reservation system not having feature of displaying appropriate messages for events and errors which occur while accessing the system. Proper validation and session has not been setup by which it system not able to identify and differentiate users, so cannot be used appro...

  Session 13: Develop “Railway Reservation System” as per specifications given in Sessions 1, 3,   4,5 and 6.   Project Proposal  The Project “Railway Reservation” deals with the automation of the reservation and enquiry of the railway reservation system.  It maintains all information starting from reservation to cancellation of tickets. It also acts as an enquiry system about the different trains available. It gives the details of the distance, arrival time and departure time of the different trains. The computerization is aimed at job simplification and reducing the manual work and effective record maintenance. Introduction The introduction of the Software Requirements Specification (SRS) provides an overview of the entire SRS purpose, scope, definitions, acronyms, abbreviations, references and overview of SRS.A Software Requirements Specification (SRS) - a requirements specification for a softw...