SE-1 Flashcards

1
Q

Software?

A

Software is a set of instructions, data or
programs used to operate computers and
execute specific tasks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

System software

A

A collection of programs designed to
operate, control, and extend the processing
capabilities of the computer itself

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Application software

A

Designed to satisfy a particular need of a
particular environment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

System Software examples

A

Operating system
Compilers
Interpreters
Device drivers
Assemblers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Explain about the application software

A

A user interacts directly assist the user in doing specified tasks.

may consist of a single program Eg :- MS notepad -writing and editing a simple text.

Also consist of a collection of programs
Eg :- MS office package

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Application software examples

A

*Payroll Software
* Student Record Software
* Inventory Management
Software
* Railways Reservation Software
* Microsoft Office Package –
Word , Excel . PowerPoint , Access
etc..

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

System?

A

Collection of components
that are work together to
perform a specific /
common task

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

NATURAL SYSTEMS

A

*Exists in natural

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

FABRICATED SYSTEMS

A

Built by people

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

System characteristics

A

Boundary
Relationships
Components

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Boundary meaning

A

Boundary : separation
between a system & its
environment that
inputs & outputs must
cross

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Information System

A

Combine information , technology , people , data
to support business activities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Information system components

A

*Hardware : Physical layer of the information system
* Software : Programs that control the hardware &
produce the desired results.
* Data : Raw materials/facts that are transformed into
useful information.
* Processors : Takes & business functions that users
perform to achieve results.
* People : who interact with the information system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Information system elements

A

*Input : data entered to the system
*Process: converting data into
information.
*Output :final result / output
*Storage : saving

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Information system types

A

➢ Transaction processing systems (TPS)
➢ Management Information systems (MIS)
➢ Decision Support system(DSS)
➢ Executive Information System (EIS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

TPS

A

Goal : to improve transaction processing with
fewer people.
*Used by operational staff.

16
Q

MIS

A

*Generates detailed, summary & exception
reports.
*Used by low-level managers to make short
term decisions.

17
Q

DSS

A

use of underlying models &
algorithms to support decision
making.
*Used by middle-level managers who
make decisions under certain
situations.

18
Q

EIS

A

*Used by top-level managers
*Helps to make strategic decisions.
*Affects for the long-term running for
an organization.

19
Q

SW process?

A

A set of ordered tasks involving activities, constraints
and resources that produce a software system.

imposes consistency and structure on a
set of activities

20
Q

Life-cycle?

A

The process of building a product is sometime called a
lifecycle

21
Q

SDLC?

A

SDLC is the entire process of
building , deploying , using & updating information system

22
Q

SDLC phases?

A
  • Planning
  • Analysis
  • Design
  • Implementation
  • Support
23
Q

SDLC models

A

Predictive approach

*system can be developed according to the plan

Adaptive approach

*the project can’t be planned out completely in advance but must be
modified as it progresses.

24
Q

SDLC models examples

A

➢Waterfall model
➢Incremental model
➢Spiral model
➢RAD model
➢Prototyping

25
Q

Explain about the waterfall model.

A
  • A linear-sequential life-cycle model.
  • Very simple to understand and use.
  • All the phases are cascaded to each other.
  • Each phase must be completed before the next
    phase can begin and there is no overlapping in
    the phases
26
Q

Requirement Analysis

A

requirement specification
document.
* Requirement gathering techniques
➢ Questionnaires
➢ Interviews
➢ Document sampling
➢ Observations

27
Q

System Design

A

system design is prepared.
* Specifying hardware and system requirements
* Defining the overall system architecture.

28
Q

IMPLEMENTATION/CODING

A
  • The design must be translated to a machine
    readable form.
  • The software design is realized as a set of
    programs or program units.
  • Programming languages or tools can be used to
    develop software.
29
Q

TESTING

A
  • All the units developed in the implementation phase are
    integrated into a system after testing of each unit.
  • Post integration the entire system is tested for any faults and
    failures.
30
Q

Testing types

A

➢Unit testing
➢Integration testing
➢System testing
➢Acceptance testing

31
Q

Deployment

A

The product is released to the actual environment.
(customer usage)

32
Q

Maintenance

A

*There are some issues which come up in the
client environment.
* To fix those issues, patches are released.
*Also to enhance the product some better
versions are release

33
Q

Waterfall model-Advantages

A
  • Simple and easy to understand and use
  • Easy to arrange tasks.
  • Works well for smaller projects where requirements are
    very well understood.
  • Well understood milestones.
  • Phases are processed and completed one at a time.
  • Clearly defined stages.
34
Q

Waterfall model-Disadvantages

A
  • Not a good model for complex and object-oriented
    projects.
  • Poor model for long and ongoing projects.
  • High amounts of risk and uncertainty.
  • Not suitable for the projects where requirements are at
    a moderate to high risk of changing.
  • It is difficult to measure progress within stages.
  • Cannot accommodate changing requirements.