SYSTEM ANALYSIS AND DESIGN

BCA 3RD SEMESTER ( UNIT 1)

SYSTEM DEVELOPMENT FUNDAMENTALS
PREPARED BY:
PARICHAYA ADHIKARI
 Introduction to System
 A system is a group of interrelated components working together towards a
common goal by accepting inputs and producing outputs in an organized
transformation process.
For eg: College system, Economic system, Language System, a business and its
parts , Marketing sales , Research, Shipping, etc.
Fig: Basic system Model
 System (Elements)
 System (Elements)
 Input: Input is what data the system receives to produces
a certain output.
 Output: what goes out from the system after being
processed is known as output.
 Processing : The process involved to transform input into
output is known as processing.
 Control: In order to get the desired results it is essential to
monitor and control the input , processing and the output
of the system.
 System (Elements)
 Feedback: The output is checked with the desired standards
of the output set and the necessary steps are taken for
achieving the outputs as per the standards , this process is
called as feedback.
 It helps to achieve a much better control in the system.
 Boundaries: The boundaries are nothing but the limit of the
system.
 Environment : The things outside the boundary of the system
are known as environment. Change in the environment
affects the working of the system.
 Interfaces: The inter connections and the interactions
between the sub system is known as the interfaces.
 System (Characteristics )
 Organization
 It is the arrangement of components that helps to
achieve objectives.
 Interaction
 Each component of system interact with another
component of the system.
 Interdependence
 They are coordinated and linked together according to a
plan.
 One subsystem depends on the input of another
subsystem for proper functioning.
 System (Characteristics )
 Integration
 It refers to the completeness of system.
 Central Objective
 System must be centered.
 Information system
 Data
 Data is a representation of fact a number , a word an
image , a picture or a sound.
 Information
 Information is data that is meaningful or useful to
someone.
 Information system
 An information system is a combination of people ,
hardware , software, communications networks and data
resources that helps organize and analyze data in an
organization.
 Information system provide information to help in the
operations and management of an organization.
Eg: Information stored by college , data stored by hospital ,
Information store by bank
 Information system
  Information system (Types)
 Transaction Processing System
 TPS (system) is a type of information system that collects , stores,
modifies and retrieves the data transaction of an organization.
OR
 TPS is software for managing data transaction that are done
within or outside the organization.
 For eg: credit card transaction, payment by cheque , online
transaction, electronic transfer of funds airline reservation system ,
POS etc.
  Transaction Processing system (Types)
 Batch processing Transaction Processing System
 The processing of transactions takes place over batches.
 These batches can be customized as per organization
requirements.
For eg: a company may want to process the payroll of its employees
in a weekly or bi-weekly, Cheque clearance
 Real time processing
 Under real time processing , every single transaction is processed
with immediate effect.
 There is no time delay in the real time processing system.
For eg: bank Atms , Customer service system.
  Transaction Processing system (Function)
 Input function (Securing and inputting the data of the transaction).
 Output Function (Producing the report and record of the input
data to be used for future references).
 Storage Function: (Storing data from both input and output
operations).
 Processing Function. (Computing , calculating sorting and defining
the input data).
  Information system (Types)
 Management Information system
 Management
 The process of dealing with or controlling things or people
management function include , Planning , organizing ,directing
and controlling.
 Information
 Data which has been processed in such a way that it becomes
meaningful to a person is referred to as information.
 System
 A system is a collection of elements or components that are
organized for a common purpose.
  Information system (Types)
 Management Information system
 MIS is a computer based system that converts data from
transaction processing system (TPS) into inform of summarized
reports and deliver those reports to the managers for carrying out
the function of management.
 MIS is used by middle level management to take decisions
effectively and implement the operations accordingly.
 MIS is used to generate daily , weekly of monthly reports in various
form such as tables with numerical values or visual displays such as
graphs.
  Information system (Types)
 Management Information system (Function)
 Data capturing (MIS capture data from various internal and
external sources of the organization).
 Process of data (Processing of data is done by such activities as
calculating , sorting, classifying and summarizing).
 Storage of information (Save organization record for later use).
 Retrieval of information.
 Dissemination of information.
  Information system (Types)
 Decision support system
 A decision support system DSS is a computer based application
that collects organizes and analyzes business data to facilitate
quality business decision making for management, operations and
planning.
 Interactive information system designed to assist decision makers in
organization.
 DSS analysis helps companies to identify and solve problems and
make decisions.
 Consists: Hardware , Software , data mathematical and statistical
models.
 For eg: Logistic system, Financial Planning system etc.
  Information system (Types)
 Decision support system (Function)
 Model Building (Identifying the most appropriate model for solving
problems)
 Risk Analysis ( Helpful while taking medium of high risks decision )
 Goal oriented
 Graphical Analysis (large volume of data in graphical format).
 What if analysis .
  Information system (Types)
 Decision support system (Function)
 Model Building (Identifying the most appropriate model for solving
problems)
 Risk Analysis ( Helpful while taking medium of high risks decision )
 Goal oriented
 Graphical Analysis (large volume of data in graphical format).
 What if analysis.
  Information system (Types)
 Artificial intelligence information system.
 AI intelligent system that are capable of learning , reasoning,
adapting and performing tasks similar to humans.
 AI information technology systems are concerned with capturing ,
storing , analyzing and evaluating data to communicate the best
output as a piece of information.
 AI system are considered more intelligent than information system.
  Information system (Types)
 Expert information system.
 An expert information system is a computer program that is
designed to solve complex problems and to provide decision
making ability like a human expert.
 It performs this by extracting knowledge from its knowledge base
using the reasoning and inference rules according to the user
queries.

  Information system (Types)
 Expert information system.
 A reporting tool (Software)
 Allows you to turn your organization data into useful summarize
reports.
 These reports are generally used by executive level managers for
quick access to reporting coming from all company levels and
departments.
  Information system (Types)
 Office automation system.
 Office automation refers to the varied computer machinery and
software used to digitally create collect, store , manipulate and
relay office information needed for a accomplishing basic tasks.
 OAS is an information system which is computer based that
collects , process , stores and transmits electronic messages.
 OAS are the combination of networked computer hardware and
software also people in information system.
  Information system (Types)
 Office automation system. (Function)
 Electronic publishing. (Word publishing and desktop publishing)
 Electronic Communication. (Email , Voice mail, Fax)
 Electronic collaboration (Electronic meeting).
 Image processing (Electronic document management,
Multimedia system).
 Office management (Office accessories, electronic scheduling
and task management).
  System analysis and design Overview
 System Analysis
 It is the process of collecting and interpreting facts , identifying the
problems and decomposition of a system into it’s components.
 Understanding the goals and strategies of the system.
 Defining the information requirements that support those goals
and strategies.
 It is not about programming.
 Investigation of the problem and requirement rather than solution.
  System analysis and design Overview
 System Analyst
 A System professionals who uses system analysis and design
techniques to solve system problems using information technology.
 A system analyst keep up to date with the latest technology to
improve productivity at all times for an organization.
  System analysis and design Overview
 System Analyst (Roles)
 System Knowledge delivery .
 System Problem solver. (Identify and removing unnecessary data
problem).
 Help translate system requirements into IT projects.
 Defining user requirements. (Observing users and their
requirements from a system , can done from interviews meeting)
 Prioritizing requirements (choose or prioritize the best req among
various requirements).
 System Design and evaluation.
 Keeping up to date with technological advancements.
  System analysis and design Overview
 System Analyst (Skills )
 Communication skills
 Critical Thinking
 System analytics
 Technical Analysis
 Management.
  System analysis and design Overview
 System Design
 A conceptual solution that fulfills the requirements, rather than
implementation.
 The process of defining the architecture components , modules ,
interfaces and data for a system to satisfy specified requirements.
 For system design major elements used were software tools ,
format methods , well defined processes that use methodologies
like OOP , CASE tools , ER, DFD etc.
 System Development Life Cycle
 SDLC is the process of understanding how an information system (IS) can support
business needs by designing a system, building it and delivering it to users.
 SDLC includes phases such as planning, analysis , design , implementation and
maintenance.
  System Development Life Cycle (Phases)
 Planning and requirements analysis.
 Defines needed information, function behavior , performance and interfaces.
 Analyze requirements to form an initial software model.
 Includes calculating labor and materials costs creating timetables, creating
projects teams and leadership structure.
 Define scope and purpose of the software.
 Done by the customers.
  System Development Life Cycle (Phases)
 Design.
 Detailed definition of inputs/outputs and processes including data structures ,
software structure etc.
 Define overall system architecture.
 Define user interface , platforms , programming , security about software.
 Reviewed by customers.
 Logical design
 Physical design.
  System Development Life Cycle (Phases)
 Implementation / code.
 Programmers begin working on writing code to meet user requirement.
 The software team creates the actual software.
 The solution is transferred from paper to action.
 Tasks include acquire new equipment, hiring new employee, Training employees.
 Planning and designing the system’s physical layout.
  System Development Life Cycle (Phases)
 Testing.
 It helps to ensure that their products fulfills the clients need or not.
 Helps to identify bugs and errors in the software.
 Based on the requirements develop and execute unit test cases, integration test
cases load and performance Test cases and also user acceptance testing.
  System Development Life Cycle (Phases)
 Maintenance.
 Maintenance phase of the SDLC occurs after the product is in full operation.
 Include software upgrades, repairs and fixes of the software if it breaks.
 Software Enhancement.
  System Development Life Cycle (Model)
 Water Fall Life Cycle Model (Traditional)

  System Development Life Cycle (Model)
 Water Fall Life Cycle Model
 First Life cycle models.
 Developed by Winston W. Royce 1970.
 It is also referred to as a linear sequential life cycle model.
 Top down view .
 In this model each phase must be completed before the next phase can begin
and there is no overlapping the phases.
  System Development Life Cycle (Model)
 When suitable a waterfall model
 Requirement are very well documented , clear and fixed .
 Product definition is stable.
 Technology is under stable and is not dynamic.
 When the project is short.
  System Development Life Cycle (Model)
 Waterfall model (Advantages)
 Simple and easy to understand and use
 Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Clearly defined stages.
 Well understood milestones.
 Easy to arrange tasks.
 Process and results are well documented.
  System Development Life Cycle (Model)
 Waterfall model (Disadvantages)
 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high risk of
changing. So, risk and uncertainty is high with this process model.
 It is difficult to measure progress within stages.
 Cannot accommodate changing requirements.
 Adjusting scope during the life cycle can end a project.
  System Development Life Cycle (Model)
 CASE tools
 CASE stands for computer Aided software engineering.
 It means development and maintenance of software projects with the help of
various automated software tools.
 CASE tools provide an overall framework for systems development and support a
wide variety of design methodologies , including structured analysis and object
oriented analysis.
  System Development Life Cycle (Model)
 Reason for using CASE tools.
 Quick installation .
 Time saving by reducing coding and testing time.
 Enrich graphical techniques and data flow.
 Optimum use of available information.
 Enhanced analysis and design development.
 Create and manipulate documentation.
 Transfer of information between tools efficiently.
 The speed during the system development increased.
 To increase speed of development and design.
  System Development Life Cycle (Model)
 Types of CASE Tools.
 Diagram tools
 It helps in diagrammatic and graphic representations of the data and system
processes.
 It includes system elements control flow and data flow among different software
components.
For eg: flow chart maker tool.
 Computer display and report generator.
 It helps in understanding the data requirements and the relationships.
For eg: Dbxtra software (for report generator)
  System Development Life Cycle (Model)
 Types of CASE Tools.
 Analysis tools
 It focuses an inconsistent , incorrect specification involved in the diagram and
data flow.
 It helps in collecting requirements , automatically check for any irregularity ,
imprecision in the diagrams, data redundancies erroneous omissions.
For eg: Accept 360 , visible Analysit , Accompa etc.
 Central Repository.
 It provide the single point of storage for data diagram , reports and documents
related to project management.
For eg: Data dictionary (defines data about data metadata )
  System Development Life Cycle (Model)
 Types of CASE Tools.
 Documentation generators.
 It helps in generating user and technical documentation as well as creates
documents for technical users and end users.
For eg: Doxygen , Drexplain , Adobe Robot help for documentation.
 Code generators.
 It aids in the auto generation of code including definitions with the help of designs
, documents and diagrams.
  System Development Life Cycle (Model)
 Prototype Model .
 A prototype model suggest that before carrying out the development of the
actual software a working prototype of the system should be built.
 A prototype is a toy implementation of the system.
 Prototype is a working model of software with some limited functionality.
 Prototyping is used to allow the users evaluate the developer proposals and try
them out before implementation.
  System Development Life Cycle (Model)
 Prototype Model (Types)
 Rapid throwaway Prototyping
 In this method developers can explore the ideas as well as get proper customer
feedback.

 Evolutionary Prototyping
 In this method we developed prototype according to the customer opinion.
 System Development Life Cycle (Model)
 Prototype Model (Phases)
  System Development Life Cycle (Model)
 Prototype Model (Phases)
 Requirement Gathering:
 Begins with requirements analysis and the requirements of the system
(interviewed, questionnaires , meeting).
 Quick Design
 Give an idea of the system to the user.
 A quick design helps in developing the prototype.

 Build Prototype
 Represent the working model of the required system.
  System Development Life Cycle (Model)
 Prototype Model (Phases)
 User Evaluation:
 Comments and suggestions are collected from the users and provided to the
developer.
 Refining Prototype.
 If user is not satisfied , the prototype is refined according to the user requirement.
 Engineer Product
  System Development Life Cycle (Model)
 Need of the Prototype Model
 Prototype provides a method to example design problems and evaluating
solutions.
 The development of the prototype model is expensive but is a good model
because it satisfy all the requirements of the customers.
  System Development Life Cycle (Model)
 Advantage of Prototype Model
 This model is flexible in design.
 It is easy to detect errors .
 We can find missing functionality easily.
 New requirements are easily accommodated.
 Project reused by developer in the future.
 Greater level of customer satisfaction and comfort.
 It can actively involve users in the development phase.
  System Development Life Cycle (Model)
 Disadvantage of Prototype Model
 This model is costly.
 It is a time consuming if customer asks for changes in prototype.
 Customer may get confused in the prototype and real systems.
  System Development Life Cycle (Model)
 Rapid application development Model
 RAD model is a software development process based on prototyping without any
specific planning.
 It targets at developing software in a short span of time.
  System Development Life Cycle (Model)
 Rapid application development Model (Phases)
 Requirements Planning Phases
 During this phase developers , clients (software users ) and team members
communicate to determine the goal and expectations for the project.
 Defining the requirements (Time , Cost, manpower etc) of the projects.
  System Development Life Cycle (Model)
 Design workshops (Phase)
 During this phase users respond to actual working prototypes and analysis refine
designed modules based on user response.
 Preparation for rapid construction.
 Program and application development .
 Coding.
 Unit, integration and system testing.
 Work with users to design system.
  System Development Life Cycle (Model)
 Implementation Phase.
 This is the implementation phase where the finished product goes to launch.
 It includes data conversion testing and change over to the new system as well as
user testing. .
  System Development Life Cycle (Model)
 Spiral Model
 The spiral model is a system development lifecycle (SDLC) method used for risk
management that combines the iterative development process model with
elements of the waterfall model.
 Each phase of spiral model in s/w begins with a design goal and ends with the
client reviewing the progress.
 The spiral model in SE was first mentioned by barry Boehm (1989).
  System Development Life Cycle (Model)
 Spiral Model (Phases)
 Object determination and identify alternative solution. (First Phase)
 Requirements are gather form customer.
 Objectives are identified , elaborated and analyzed at the start of every phase.
 Estimating cost , schedule and resources for the iteration.
 Identify and resolve Risks (Second Phase)
 All the possible solution are identified and select the best possible solution.
 Risks associated with the solution is identified and the risks are resolved.
 Identification of potential risks.
  System Development Life Cycle (Model)
 Spiral Model (Phases)
 Develop next vision of the product (Third Phase)
 It includes testing , coding and deploying software at the customer site.
 Review and plan for next phase (Fourth Phase)
 It includes identifying and monitoring risks.
 Evaluation of S/W by the customer.
  System Development Life Cycle (Model)
 When to use spiral Model
 When project is large.
 Creation of a prototype is applicable.
 Applicable for medium to high risk projects.
 When changes may require at any time.
  System Development Life Cycle (Model)
 Advantages of spiral Model.
 Project monitoring is easy.
 Suitable for high risk project.
 Reduces the number of risk.
 Changes may be accommodated in late stages.
 Good for large and mission critical projects.
  System Development Life Cycle (Model)
 Disadvantages of spiral Model.
 No suitable for low risk projects.
 Cost of this approach is usually high.
 Strict rules and protocols are followed.
 Can be costly model to use.
 Does not work well for smaller projects.
 System Development Life Cycle (Model)
 Agile SDLC
  System Development Life Cycle (Model)
 Agile SDLC
 Agile SDLC model is a combination of iterative and incremental process models
with focus on process adaptability and customer satisfaction by rapid delivery of
working S/W product.
 Agile methods breaks the product into small incremental builds.
 Each iteration typically last from certain months or weeks .
 In Agile the tasks are divided to time boxes (Small time frames) to deliver specific
features for a release.
 The final iteration build holds all the features required by the customer.
  System Development Life Cycle (Model)
 Agile SDLC manifesto was published in 2001. (manifesto principle)
 Individuals and interactions (self – organization , motivation)
 Working S/w (Demo working s/w is considered)
 Customer collaboration .
 Responding to change (Focus on quick responses to change).
  System Development Life Cycle (Model)
 Developmental Process for an Agile Project
 Exploration (environment , problem , assemble the team, team member access,
estimate time cost, work environment etc)
 Planning (Planning date , cost and fixed , Interface , design , rules and
regulations expense limiting , risk , possible solutions ,
 Iterations to the First release (cycle testing , Feedback , change , Customer written
functional test,
 Productionizing (product is released )
 Maintenance
  System Development Life Cycle (Model)
 Agile SDLC manifesto was published in 2001. (manifesto principle)
 Individuals and interactions (self – organization , motivation)
 Working S/w (Demo working s/w is considered)
 Customer collaboration .
 Responding to change (Focus on quick responses to change).
  System Development Life Cycle (Model)
 Agile SDLC (Advantages of agile model)
 Very realistic approach to S/W development.
 Promotes teamwork and cross training .
 Functionality can be developed rapidly and demonstrated.
 Resource requirements are minimum .
 Suitable for fixed for changing requirements.
 Easy to manage.
 Minimal rules , documentation easily employed.
 Gives flexibility to developers.
  System Development Life Cycle (Model)
 Agile SDLC (disadvantages of agile model)
 Not suitable for handling complex dependencies.
 More risk of sustainability , maintainability and extensibility.
 Depends heavily on customer interaction so if customer is not clear team can be
driven in the wrong direction.
 Lack of documentation.
  System Development Life Cycle (Model)
 Extreme Programming
 XP is most important software development frameworks of agile model.
 Used to improve Software quality according to customer requirements.
  System Development Life Cycle (Model)
 Extreme Programming (Continue….)
( Some of the good practices that have been recognized in the extreme
programming are as follow) .
 Code review (Detect and correct error , review of written code between
programmers due to pair programming).
 Testing ( removes error and improves its reliability)
 Incremental Developmental (According to customer feedback development
team come with new increment )
 Simplicity (easier to develop, understand, as well as debug and test)
 Design ( Good quality software design develop good quality software)
 Integration Testing ( identify bugs at the interface)
  System Development Life Cycle (Model)
 Extreme Programming (Principles)
 Coding (include modern coding, drawing diagrams (Modeling) , Scripting (web
based system )
 Testing (Provide fault free software )
 Listening (Developers need to carefully listen to the customers)
 Designing (proper design )
 Feedback
 Simplicity
  System Development Life Cycle (Model)
 Extreme Programming (Applications)
 Small Projects
 Project involving new technology or research projects.
  System Development Life Cycle (Model)
 Extreme Programming (Advantages )
 Slipped Schedules: (Timely Deliveries)
 Cancelled Projects.
 Costs incurred in changes. (For changing environment current operations are not
affect)
 Production and post delivery defects : Emphasis is on: (due to unit text early
detect and fixed error in early stage).
 Misunderstanding the business and / or domain.
 Business changes
 Staff turnover
  System Development Life Cycle (Model)
 Extreme Programming (Disadvantages )
 Difficulty
 XP relies on very many factors. (High risk )
 Code Centric (code centric rather than Design Centric)
  System Development Life Cycle (Model)
 Modern Waterfall Modern
 Difficulty
 XP relies on very many factors. (High risk )
 Code Centric (code centric rather than Design Centric)
  System Development Life Cycle
 Service oriented Architecture
 Idea behind SOA is to build system around generic services or specific business
function which can be used in many different application.
 Once a set of services have been identified and validated , developers can
assemble them into new applications.
 SOA is a middleware solution which makes two or more systems or applications to
talk each others.
 Failure of one system does not impact on other system.
  System Development Life Cycle
 Service oriented Architecture
 An example of a service is a credit check.
 Any application that deals with customers or suppliers would have credit check.
 For an SOA approach to be successful a large number of services would
available for various application to access.
  System Development Life Cycle
 Service oriented Architecture
 eg
  System Development Life Cycle
 Service oriented Architecture
 In order to setup an SOA , the services must be :
 Modular (process of subdividing a computer program into separate sub
program).
 Reusable
 Work together with other modules (interoperability)
 Able to be categorized and identified
 Able to monitored
 Comply with industry specific standards.
  System Development Life Cycle
 Object – oriented Analysis and design
 The object oriented approach combines data and process (Method) into single
entities called objects.
 Objects usually corresponds to the real things an information system deals with
such as customers , suppliers contracts etc.
 The goal of OOAD is to make systems elements more reusable thus improving
system quality and the productivity of systems analysis and design .
  Managing the information system project.
 Project management
 Project is defined as a sequence of tasks that must be completed to attain a
certain outcome.
 Project management is the process of leading the work of a team to achieve all
project goals with in the given constraints.
 IT project management
 IT project management includes overseeing projects for software developments ,
hardware installations , network upgrades , cloud computing and virtualization ,
business analytics and data management.
 It project managers are responsible for planning , budgeting , executing , leading
, troubleshooting and maintaining these projects.
  Managing the information system project.
 Shaping a project
 (completed with in time , budget, and deliver a quality product , satisfies users
and meet requirements )
 Triple constraints of project

  Managing the information system project.
 Triple constraints of project
 Scope
 It define what is part of the project it’s purpose , objectives , boundaries and the work
needed to achieve the final deliverable.
 (activities, Plan , vision , result , product, service , requirements , expectations)
 Time
 (Schedule project activities , Schedule back on track )
 It is the estimated total amount of time the project team needed to complete all the tasks
and deliver the final result.
 Cost
 ( hiring resources needed to complete the project).
 Human resources , other resources
 Managing the information system project.
 Project life Cycle
  Managing the information system project.
 Project life Cycle
 Initiation Phase
 (Vision , feasibility study , identify problem , scope , goals , risks , defining
project , resources , Cost).
 Why a project was undertaken? What problems need to be addressed?
 What needs, objectives and profits were served by this project?
 - Who are the key stakeholders, sponsors and project team?
 - What are the roles and responsibilities of each person associated with the
project?
  Managing the information system project.
 Project life Cycle
 Planning Phase
 Planning is at the heart of the project life cycle and tells
everyone involved where you are going and how you are going
to get them.
 Creating project plan , resource , financial, quality, risk ,
communication , Acceptance )
  Managing the information system project.
 Project life cycle
 Execution
 Is about building deliverables that satisfy the customer.
 Allocating resources and keeping team members focused on their
assigned tasks
 Assemble execution phase project team.
 Team development.
 Assign resource.
  Managing the information system project.
 Project life cycle
 Monitor
 IT project manager leads the entire team. The end goal is the deliverable
product or service.
 Execute project management plans.
 Conduct progress status meetings.
 Update project schedule and management plans.

  Managing the information system project.
 Project life cycle
 Closure
 Handover all deliverables to your customer.
 Gather the core team to invite feedback about what worked and what
didn't.
  Managing the information system project.
 Project Managers skills
 Leadership , communication , management
 Customer relation , Technical problem solving
 Conflict management , Team management , Risk and change management
  Managing the information system project.
 Project Management importance
 Project management allocate and manage resources in such a manner that it takes
the organization towards it’s goal and success.
 It helps to reduce the risk of the project.
 Efficient project management system give customer end user satisfied and pays a
vital role in the new global economy.
 For better collaboration and productivity (B2C , C2C).
 Managing remote employees.
 Reducing costs.
 Improving data security.
  Managing the information system project.
 Project Scheduling
 A scheduling in our project time table actually consists of sequenced activities
and task that are needed to be delivered under a given period of time.
 Effective project scheduling leads to success of project reduced cost, and
increased customer satisfaction.
 Managing the information system project.
 Project Scheduling
  Managing the information system project.
 Project Scheduling
 GANTT CHART
 A Gantt chart is a visualization that helps in scheduling, managing, and
monitoring specific tasks and resources in a project.
 It consists of a list of tasks and each task's progress.
 It's the most widely used chart in project management.
 Gantt charts are used in heavy industries for projects like building dams, bridges,
and highways, as well as software development and building out of other goods
and services.
 Henry Gantt (1861-1919), an American mechanical engineer, designed the Gantt
chart.
  Managing the information system project.
 Project Scheduling
 Project Network Diagram
 A project network is a graph that shows the activities , duration and
interdependencies of tasks of project.
 Project network is usually built and designed with the help of hierarchical
diagrams and charts.
 It shows established dependencies between project tasks and processes.
 Project network diagram is helpful in defining , documentation, analyzing and
improving project tasks and activities.
 It is also called project flowchart.
Eg: Task Analytics chart.
  Managing the information system project.
 Project Scheduling
 Project Network Diagram

 where 0,1,2,3 etc are Activities , 3 is (4,5,6) predecessor (before) , 7

is (5 ,6)’s Successor (After).
  Managing the information system project.
 Project Scheduling
 CPM( Critical Path Method)
 Estimate the maximum and minimum time required to complete a
project.
 Done on critical activities.
 Critical path definition of term
 Earliest start time (ES): How early, the successor activity begins once the
predecessor activity finishes.
 Earliest Finish Time (EF): Earliest Start Time + duration of each activity.
 Latest Finish Time (LF): The latest time within which the activity finishes without
delaying the project.
 Latest Start Time (LS): Latest Finish Time – Activity duration
  Managing the information system project.
 Project Scheduling
 CPM( Critical Path Method)
  Managing the information system project.
 Project Scheduling
 PERT chart
 A program evaluation review technique (PERT) chart is a graphical
representation of a project's timeline that displays all of the
individual tasks necessary to complete the project.
 That uses optimistic , pessimistic and realistic time estimated to
calculate the expected time for particular task.
 Optimistic time reflects the minimum possible periods of time and
pessimistic time reflect the maximum possible periods of time for an
activity.
  Managing the information system project.
 Project Scheduling
 PERT chart
 The realistic time (R) or most likely time, reflects the project
manager “Best guess” made for an activity.
 ET= (o+4r+P)/6)
Where , o= optimistic completion time for an activity
r=realistic completion time for an activity
p=Pessimistic completion time for an activity
ET= expected time for the completion for an activity
  Managing the information system project.
 Project Scheduling
 Difference between PERT and CPM
PERT CPM

PERT is used for those projects where time CMP is used for those projects which are
required to complete various activities is not repetitive in nature and where one has
known with certainty. experience of handling similar projects.

Probabilistic in nature Deterministic in nature

PERT is used in Research and development. CPM is used in plant maintenance and
construction work.

PERT analysis does not consider cost CMP deals with cost
 Using project management software
 Project management tools are available to help to manage a
development project.
 Most of the project management available tools has defined
common features , ability to define and order tasks , assign
resources , easily modified task and resources.
 Project management tools are available to run on IBM compatible ,
Macintosh , mainframe and workstation based system.
 Some project management programs are as follow: (Openproj,
Bugzilla , and eGroupWare, Microsoft Project etc)
  Origins Of software
 System Acquisition
 Outsourcing
 If another organization develops or runs a computer application for your
organization that practice is called outsourcing.
 A common example of such an arrangement is a company that runs payroll
application for clients so that clients do not have to develop an independent
payroll system.
 Some organizations outsource the IT development of many of their IT functions.
 Some of the company that outsourcing and offshoring are as follow : IBM , IBM ,
CISCO, Amazon ,
  Origins Of software
 System Acquisition
 Offshoring
(Working for you and with you)
 (Working for you and with you)
 Offshoring is the relocation of a business process form one country to another.
  Origins Of software
 Advantage of outsourcing
 Reduced operating expenses.
 Flexibility.
 Exposure to new talent.
 Focusing on core business processes.
 Downsize the business by using outsourcing services.
 Managing resources.
 Time saving.
  Origins Of software
 Disadvantage of outsourcing
 Lowered quality of services.
 Miscommunication.
 Risk.
 Time Zone.
  Origins Of software
 Reasons to outsourcing
 Lowered quality of services.
 Miscommunication.
 Risk.
 Time Zone.
  Sources of software.
 We can group the sources of software into six major categories.
 Information technology services firms.
 Packaged software producers.
 Enterprise solutions software.
 Cloud computing vendors.
 Open source software
 In house developers.
  Sources of software.
 Information technology services firms.
 IT services firms help companies develop custom information system for internal
use , or they develop host and run application for customers or they provide other
services.
 Table: Leading software firms and their development

Company Softwrae Business Sector

IBM Middleware/Application /Web Server/
Microsoft Operating System
EDS Outsourcing Services.
Accenture IT services
HP IT services
Oracle Database
Computer Science Corporation IT services.
  Sources of software.
 Packaged Software producers.
 Serve many market segments.
 Software offering range from general , broad based packages , such as general
ledgers , to very narrow , niche package , Off-the self software (any software
solution , usually a commercial one , developed for the mass market) , Pre
packaged software.
 Software companies develop software to run on many different computer
platforms, from micro companies to large mainframes.
 Software runs on all size computers from microcomputers to large mainframes.
 Eg: Microsoft , Oracle company produce a packaged software.
  Sources of software.
 Enterprise Solutions Software.
 Serve
  Sources of software.
 Cloud computing.
 The provision of computing resources including applications , over the internet ,
so customers do not have to invest in the computing infrastructure needed to run
and maintain the resources.
 The term cloud refers to a network or internet. We can say cloud is something ,
which is present at remote location.

 The applications provider buys , installs maintains and upgrade the application
users pay on a per use basis.
 Eg: google apps, office software: office 365, google docs, zoho office
  Sources of software.
 Open source Software
 Freely available including source code.
 Developed by a community of interested people.
 Performs the same functions as commercial software .
 For eg: Linux, MySQL , Firefox,
  Sources of software.
 In house Development.
 If sufficient system development expertise with the chosen platform exists in
House , then some or all of the system can be developed by the organization’s
own staff.
 Hybrid solutions involving some purchased and some in house components are
common.
  Choosing of the shelf software
 (Off the Shelf Software), also called commercial software, is any kind
of software solution that has been developed for the mass market.
 Cost: Comparing the cost of developing the same system in house
with the cost of purchasing or licensing the s/w package.
 Functionality: The tasks that the S/W can perform and the
mandatory , essential and desired system features.
 Vendor support: Whether or how much support the vendor can
provide and at what cost.
 Choosing of the shelf software
 Viability of vendor: Can the s/w adapt to changes in systems
software and hardware.
 Flexibility: How easy it is to customize the S/W.
 Documentation : Is the use’s manual and technical documentation
under stable and up to date.
 Response Time: How long it takes the s/w package to respond to
the user’s requests in an interactive session.
 Ease of installation: A measure of the difficulty of loading the
software and making it operational.
 Validating purchased software information
 Use a variety for information sources.
 Collect information from vendor.
 Software documentation.
 Technical Market literature.
  Validating purchased software information
 Request for proposal (RFP).
 Documents provided to vendors to ask them to propose hardware
and system s/w that will meet the requirements of a new system.
 Information sources For RFP
 Vendors proposal.
 Running S/W through a series of tests.
 Feedback from other users of the vendor product.
 Independent S/W testing services.
 Article in trade publication.