CC106 PRELIM

application

• is a software program that can run on a portable device such as a smartphone or tablet.

Software

• is capable of performing many tasks, as opposed to hardware which can only perform mechanical tasks that they are designed for.

Software

 is more than just a program cod

System software

• Helps run the computer hardware and computer system itself.

Application software

• Allows users to accomplish one or more tasks. It includes word processing, web browsing and almost any other task for which you might install software.

Programming software

• is a set of tools to aid developers in writing programs. The various tools available are compilers, linkers, debuggers, interpreters and text editors.

Communication

•  An app can help you increase your communication with customers. You can promote your services through an app and build up a community through it

Support

 You can provide extra support through an app so that customers can get help wherever they may be

Convenience

Having a link to your services at the user’s fingertips will prove to be invaluable to them as they’ll no longer be tied to a computer to access your offerings

Visibility

An app offers increased visibility of your brand. Users and potential customers will be able to access your services from anywhere

Efficiency

• An app can allow you to manage your business dealings with your customers more efficiently and directly, improving the business’s processes and potentially reducing costs in the long run.

Target Audience

•  The needs of the audience should be considered in order to make an app that they want to use. Conducting user research should aid you in what it is that a user would want and how they might use it

Efficiency/ease of use

•  The user should be able to use the app easily, and it should be an enjoyable experience when using it

Doing the basics

• If for an existing product, the app should do all the basics and hopefully in less time

Stability and speed

It’s important to create an app that not only performs well and fast, but is robust and doesn’t crash

The finer details

• Once you have the form and function down, think about how you can perhaps finesse the app.

SOCIAL NETWORKING

• Companies such as Facebook, Twitter and Instagram have had apps for years allowing for ease of use when on the go.

HEALTH AND FITNESS

• As the interest in health and fitness has increased in the digital age with the rise of health blogs and fitness accounts on Instagram, so too has the availability of health and fitness apps.

ENTERTAINMENT & MUSIC

• - Streaming services have increased in popularity over the years with the rise of mobile technology.

FINANCE

• Mobile banking has become very popular as there’s often a need to manage money when on the go.

Software Evolution

The process of developing a

software product using software engineering principles 

And methods is referred to as

Continuing change

• - A software system must continue to adapt to the real world changes, else it becomes progressively less useful.

Increasing complexity

A software system evolves, its complexity tends to increase unless work is done to maintain or reduce it.

Conservation of familiarity

• The familiarity with the software or the knowledge about how it was developed, why was it developed in that particular manner etc. must be retained at any cost, to implement the changes in the system.

Continuing growth

 In order for a system intended to resolve some business problem, its size of implementing the changes grows according to the lifestyle changes of the business.

Reducing quality

• A software system declines in quality unless rigorously maintained and adapted to a changing operational environment.

Feedback systems

• The software systems constitute multi-loop, multi-level feedback systems and must be treated as such to be successfully modified or improved.

Self-regulation

• a system evolution processes are self-regulating with the distribution of product and process measures close to normal.

Organizational stability

The average effective global activity rate in an evolving a system is invariant over the lifetime of the product

Software Development Life Cycle -

, is a well-defined, structured sequence of stages in software engineering to develop the intended software product.

Communication

•  initiate the request

Requirement Gathering

•  bringing out the information on what the project requirement is

Feasibility Study

•  he team analyzes if a software

can be made to fulfill all requirements of the user

and if there is any possibility of software being no

more useful.

System Analysis

•  decide a roadmap of their plan and try to bring up the best software model

suitable for the project.

Software design

•  The inputs from users and

information gathered in requirement gathering

phase are the inputs of this step. Output will be

the logical design and the physical design

Coding

• programming phase

testing

•  End user testing

integration

integration with other entity

Implementation

•  installing the software on user machines

Operation and Maintenance

maintaining the code, the systems for patch updates

Disposition

retirement; legacy system

Waterfall Model

• is the simplest model of software development paradigm. It says the all the phases of SDLC will function one after another in linear manner.

Iterative Model

•  This model leads the software development process in iterations. It projects the process of development in cyclic manner repeating every step after every cycle of SDLC process.

Spiral Model

•  is a combination of both, iterative model and one of the SDLC model. It can be seen as if you choose one SDLC model and combine it with cyclic process

V – model

•  The major drawback of waterfall model is we move to the next stage only when the previous one is finished and there was no chance to go back if something is found wrong in later stages.

Big Bang Model

• This model is the simplest model in its form. It requires little planning, lots of programming and lots of funds. This model is conceptualized around the big bang of universe.

System Implementation

refers to activities that occur before the system is turned over to its users.

Coding

• is the process where the physical design specifications developed by the analysis team are converted into computer codes by the programming team.

Testing

 Even though IT is done during implementation, the planning for IT should start earlier in the project. IT is the process of examining a product to ascertain what defects it contains

Integration Testing -

Combining modules and testing them is called BLANK.  The use of this test is to identify errors that were not or could not be detected by unit testing individual modules

Interface incompatibility

• An example is a caller module that passes a variable of the wrong data type to a subordinate module.

Parameter values.

• A module is passed or returns a value that was unexpected (such as negative number for a price).

Run-time exceptions.

A module generates an error such as “out of memory” or “file already in use” due to conflicting resource needs

Unexpected state interactions.

. The conditions of two or more modules interact to cause complex failures

System Testing

 instead of integrating modules into programs for testing, the programs are integrated into systems.

Naturalistic Observation

• It can be very difficult for humans to explain what they do or to even describe accurately how they achieve a task.

Studying documentation:

• Procedures and rules are often written down in a

manual and these are a good source of data about

the steps involved in an activity and any regulations

governing a task.

Requirements Gathering

is a fundamental part of

any software development project.

Modularity

• Split your software into smaller pieces with

maybe maximum of 5–10 interfaces.

Maintainability

• With good software design it’s easier to maintain

the software.

Performance

• Good software design can be used to easily pinpoint

performance bottlenecks in your software — especially if the design is done to the level of that granularity.

Portability

• By including dependencies to other software

modules, such as 3rd party libraries, in to your

design makes the software much easier to port into

another environment.

Usability

• Generating a design document for your

customers from the software design is a good idea.

It provides them an overview how the software

they are about to take into use works.

Trackability

• Usually projects have requirements coming from

either a customer or from an internal source.

Deployment

• Design should also provide information what the

software deliverables are and where should they be

placed in the deployment.

Interface or High-level Design

• is the specification of the

interaction between a system and its environment.

Interface Design

• Precise description of events in the environment, or

messages from agents to which the system must respond.