Free Essay


In: Computers and Technology

Submitted By Narvin
Words 3810
Pages 16
IJCSI International Journal of Computer Science Issues, Vol. 7, Issue 5, September 2010 ISSN (Online): 1694-0814


A Comparison Between Five Models Of Software Engineering
Nabil Mohammed Ali Munassar1 and A. Govardhan2

Ph.D Student of Computer Science & Engineering

Jawahrlal Nehru Technological University Kuktapally, Hyderabad- 500 085, Andhra Pradesh, India Professor of Computer Science & Engineering Principal JNTUH of Engineering College, Jagityal, Karimnagar (Dt), A.P., India

This research deals with a vital and important issue in computer world. It is concerned with the software management processes that examine the area of software development through the development models, which are known as software development life cycle. It represents five of the development models namely, waterfall, Iteration, V-shaped, spiral and Extreme programming. These models have advantages and disadvantages as well. Therefore, the main objective of this research is to represent different models of software development and make a comparison between them to show the features and defects of each model. Keywords: Software Management Processes, Software Development, Development Models, Software Development Life Cycle, Comparison between five models of Software Engineering.

increased recently which results in the difficulty of enumerating such companies. During the previous four decades, software has been developed from a tool used for analyzing information or solving a problem to a product in itself. However, the early programming stages have created a number of problems turning software an obstacle to software development particularly those relying on computers. Software consists of documents and programs that contain a collection that has been established to be a part of software engineering procedures. Moreover, the aim of software engineering is to create a suitable work that construct programs of high quality.

1. Introduction
Computer Science


No one can deny the importance of computer in our life, especially during the present time. In fact, computer has become indispensible in today's life as it is used in many fields of life such as industry, medicine, commerce, education and even agriculture. It has become an important element in the industry and technology of advanced as well as developing countries. Now a days, organizations become more dependent on computer in their works as a result of computer technology. Computer is considered a time- saving device and its progress helps in executing complex, long, repeated processes in a very short time with a high speed. In addition to using computer for work, people use it for fun and entertainment. Noticeably, the number of companies that produce software programs for the purpose of facilitating works of offices, administrations, banks, etc, has


Computer Function


The Software engineering

Tools and techniques to solve problems

Fig. 1 Explanation of software engineering conception.

IJCSI International Journal of Computer Science Issues, Vol. 7, Issue 5, September 2010 ISSN (Online): 1694-0814


2. Software Process Models
A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective as: 1. 2. 3. 4. Specification. Design. Validation. Evolution.

concern. The pure waterfall lifecycle consists of several nonoverlapping stages, as shown in the following figure. The model begins with establishing system requirements and software requirements and continues with architectural design, detailed design, coding, testing, and maintenance. The waterfall model serves as a baseline for many other lifecycle models.

General Software Process Models are 1. Waterfall model: Separate and distinct phases of specification and development. 2. Prototype model. 3. Rapid application development model (RAD). 4. Evolutionary development: Specification, development and validation are interleaved. 5. Incremental model. 6. Iterative model. 7. Spiral model. 8. Component-based software engineering : The system is assembled from existing components. There are many variants of these models e.g. formal development where a waterfall-like process is used, but the specification is formal that is refined through several stages to an implementable design[1].

System Requirements
Software Requirements

Architectural Design

Detailed Design




Fig. 2 Waterfall Model[4].

3. Five Models
A Programming process model is an abstract representation to describe the process from a particular perspective. There are numbers of general models for software processes, like: Waterfall model, Evolutionary development, Formal systems development and Reusebased development, etc. This research will view the following five models : 1. Waterfall model. 2. Iteration model. 3. V-shaped model. 4. Spiral model. 5. Extreme model. These models are chosen because their features correspond to most software development programs.
Requirements Definition

System and Software Design

Implementation and Unit Testing

Integration and System Testing

3.1 The Waterfall Model
The waterfall model is the classical model of software engineering. This model is one of the oldest models and is widely used in government projects and in many major companies. As this model emphasizes planning in early stages, it ensures design flaws before they develop. In addition, its intensive document and planning make it work well for projects in which quality control is a major
Operation and Maintenance
Fig. 3 Waterfall model[2].

The following list details the steps for using the waterfall

IJCSI International Journal of Computer Science Issues, Vol. 7, Issue 5, September 2010 ISSN (Online): 1694-0814


model: 1 System requirements: Establishes the components for building the system, including the hardware requirements, software tools, and other necessary components. Examples include decisions on hardware, such as plug-in boards (number of channels, acquisition speed, and so on), and decisions on external pieces of software, such as databases or libraries. 2 Software requirements: Establishes the expectations for software functionality and identifies which system requirements the software affects. Requirements analysis includes determining interaction needed with other applications and databases, performance requirements, user interface requirements, and so on. Architectural design: Determines the software framework of a system to meet the specific requirements. This design defines the major components and the interaction of those components, but it does not define the structure of each component. The external interfaces and tools used in the project can be determined by the designer. Detailed design: Examines the software components defined in the architectural design stage and produces a specification for how each component is implemented. Coding: Implements specification. the detailed design

starting coding. There is no overlap between stages. In real-world development, however, one can discover issues during the design or coding stages that point out errors or gaps in the requirements. The waterfall method does not prohibit returning to an earlier phase, for example, returning from the design phase to the requirements phase. However, this involves costly rework. Each completed phase requires formal review and extensive documentation development. Thus, oversights made in the requirements phase are expensive to correct later. Because the actual development comes late in the process, one does not see results for a long time. This delay can be disconcerting to management and customers. Many people also think that the amount of documentation is excessive and inflexible. Although the waterfall model has instructive because it emphasizes project development. Even if one model, he must consider each of relationship to his own project [4].  1. 2. 3. 4. 5. 6.  1. 2. its weaknesses, it is important stages of does not apply this these stages and its



5 6

Testing: Determines whether the software meets the specified requirements and finds any errors present in the code. Maintenance: Addresses problems and enhancement requests after the software releases.

Advantages : Easy to understand and implement. Widely used and known (in theory!). Reinforces good habits: define-before- design, design-before-code. Identifies deliverables and milestones. Document driven, URD, SRD, … etc. Published documentation standards, e.g. PSS-05. Works well on mature products and weak teams. Disadvantages : Idealized, doesn’t match reality well. Doesn’t reflect iterative nature of exploratory development. 3. Unrealistic to expect accurate requirements so early in project. Software is delivered late in project, delays discovery of serious errors. Difficult to integrate risk management. Difficult and expensive to make changes to documents, ”swimming upstream”. Significant administrative overhead, costly for small teams and projects [6]. Pure Waterfall


In some organizations, a change control board maintains the quality of the product by reviewing each change made in the maintenance stage. Consider applying the full waterfall development cycle model when correcting problems or implementing these enhancement requests. In each stage, documents that explain the objectives and describe the requirements for that phase are created. At the end of each stage, a review to determine whether the project can proceed to the next stage is held. Your prototyping can also be incorporated into any stage from the architectural design and after. Many people believe that this model cannot be applied to all situations. For example, with the pure waterfall model, the requirements must be stated before beginning the design, and the complete design must be stated before

4. 5. 6. 7. 

This is the classical system development model. It consists of discontinuous phases: 1. 2. 3. Concept. Requirements. Architectural design.

IJCSI International Journal of Computer Science Issues, Vol. 7, Issue 5, September 2010 ISSN (Online): 1694-0814


4. 5. 6.

Detailed design. Coding and development. Testing and implementation.
Table 1: Strengths & Weaknesses of Pure Waterfall

Risk reduction spirals can be added to the top of the waterfall to reduce risks prior to the waterfall phases. The waterfall can be further modified using options such as prototyping, JADs or CRC sessions or other methods of requirements gathering done in overlapping phases [5].



3.2 Iterative Development
The problems with the Waterfall Model created a demand for a new method of developing systems which could provide faster results, require less up-front information, and offer greater flexibility. With Iterative Development, the project is divided into small parts. This allows the development team to demonstrate results earlier on in the process and obtain valuable feedback from system users. Often, each iteration is actually a mini-Waterfall process with the feedback from one phase providing vital information for the design of the next phase. In a variation of this model, the software products, which are produced at the end of each step (or series of steps), can go into production immediately as incremental releases.

Minimizes planning overhead since it can be done up front. Structure minimizes wasted effort, so it works well for technically weak or inexperienced staff.

 

Inflexible Only the final phase produces a nondocumentation deliverable. Backing up to address mistakes is difficult.

 Pure Waterfall Summary The pure waterfall model performs well for products with clearly understood requirements or when working with well understood technical tools, architectures and infrastructures. Its weaknesses frequently make it inadvisable when rapid development is needed. In those cases, modified models may be more effective.  Modified Waterfall

The modified waterfall uses the same phases as the pure waterfall, but is not based on a discontinuous basis. This enables the phases to overlap when needed. The pure waterfall can also split into subprojects at an appropriate phase (such as after the architectural design or detailed design).

Table 2: Strengths & Weaknesses of Modified Waterfall



 

More flexible than the pure waterfall model. If there is personnel continuity between the phases, documentation can be substantially reduced. Implementation of easy areas does not need to wait for the hard ones.

Milestones are more ambiguous than the pure waterfall. Activities performed in parallel are subject to miscommunication and mistaken assumptions. Unforeseen interdependencies can create problems.

Fig. 4 Iterative Development.

3.3 V-Shaped Model
Just like the waterfall model, the V-Shaped life cycle is a sequential path of execution of processes. Each phase must be completed before the next phase begins. Testing is emphasized in this model more than the waterfall model. The testing procedures are developed early in the life cycle before any coding is done, during each of the phases preceding implementation. Requirements begin the life cycle model just like the waterfall model. Before

Modified Waterfall Summary

IJCSI International Journal of Computer Science Issues, Vol. 7, Issue 5, September 2010 ISSN (Online): 1694-0814


development is started, a system test plan is created. The test plan focuses on meeting the functionality specified in requirements gathering. The high-level design phase focuses on system architecture and design. An integration test plan is created in this phase in order to test the pieces of the software systems ability to work together. However, the low-level design phase lies where the actual software components are designed, and unit tests are created in this phase as well. The implementation phase is, again, where all coding takes place. Once coding is complete, the path of execution continues up the right side of the V where the test plans developed earlier are now put to use.  1. 2. 3. Advantages Simple and easy to use. Each phase has specific deliverables. Higher chance of success over the waterfall model due to the early development of test plans during the life cycle. Works well for small projects where requirements are easily understood.


System Test Planning

System Testing

High Level Design

Integration Test Planning

Integration Testing

Low Level Design

Unit Test Planning

Unit Testing


Fig. 6 V-Shaped Life Cycle Model[7].

3.4 Spiral Model
The spiral model is similar to the incremental model, with more emphases placed on risk analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. A software project repeatedly passes through these phases in iterations (called Spirals in this model). The baseline spiral, starting in the planning phase, requirements are gathered and risk is assessed. Each subsequent spiral builds on the baseline spiral. Requirements are gathered during the planning phase. In the risk analysis phase, a process is undertaken to identify risk and alternate solutions. A prototype is produced at the end of the risk analysis phase. Software is produced in the engineering phase, along with testing at the end of the phase. The evaluation phase allows the customer to evaluate the output of the project to date before the project continues to the next spiral. In the spiral model, the angular component represents progress, and the radius of the spiral represents cost.


Fig. 5 V-Model [3]

 1. 2. 3. 4.

Disadvantages Very rigid like the waterfall model. Little flexibility and adjusting scope is difficult and expensive. Software is developed during the implementation phase, so no early prototypes of the software are produced. This Model does not provide a clear path for problems found during testing phases [7].

 1. 2. 3.  1. 2. 3. 4.

Advantages High amount of risk analysis. Good for large and mission-critical projects. Software is produced early in the software life cycle. Disadvantages Can be a costly model to use. Risk analysis requires highly specific expertise. Project’s success is highly dependent on the risk analysis phase. Doesn’t work well for smaller projects [7].

IJCSI International Journal of Computer Science Issues, Vol. 7, Issue 5, September 2010 ISSN (Online): 1694-0814


Spiral model sectors Objective setting :Specific objectives for the phase are identified. 2. Risk assessment and reduction: Risks are assessed and activities are put in place to reduce the key risks. 3. Development and validation: A development model for the system is chosen which can be any of the general models. 4. Planning: The project is reviewed and the next phase of the spiral is planned [1].

 1.

under which the system would produce win-lose or loselose outcomes for some stakeholders. 3. Identify and Evaluate Alternatives: Solicit suggestions from stakeholders, evaluate them with respect to stakeholders' win conditions, synthesize and negotiate candidate win-win alternatives, analyze, assess, resolve win-lose or lose-lose risks, record commitments and areas to be left flexible in the project's design record and life cycle plans. 4. Cycle through the Spiral: Elaborate the win conditions evaluate and screen alternatives, resolve risks, accumulate appropriate commitments, and develop and execute downstream plans [8].

3.5 Extreme Programming
An approach to development, based on the development and delivery of very small increments of functionality. It relies on constant code improvement, user involvement in the development team and pair wise programming . It can be difficult to keep the interest of customers who are involved in the process. Team members may be unsuited to the intense involvement that characterizes agile methods. Prioritizing changes can be difficult where there are multiple stakeholders. Maintaining simplicity requires extra work. Contracts may be a problem as with other approaches to iterative development.

Fig. 7 Spiral Model of the Software Process[1].

 WinWin Spiral Model The original spiral model [Boehm 88] began each cycle of the spiral by performing the next level of elaboration of the prospective system's objectives, constraints and alternatives. A primary difficulty in applying the spiral model has been the lack of explicit process guidance in determining these objectives, constraints, and alternatives. The Win-Win Spiral Model [Boehm 94] uses the theory W (win-win) approach [Boehm 89b] to converge on a system's next-level objectives, constraints, and alternatives. This Theory W approach involves identifying the system's stakeholders and their win conditions, and using negotiation processes to determine a mutually satisfactory set of objectives, constraints, and alternatives for the stakeholders. In particular, as illustrated in the figure, the nine-step Theory W process translates into the following spiral model extensions: 1. Determine Objectives: Identify the system life-cycle stakeholders and their win conditions and establish initial system boundaries and external interfaces. 2. Determine Constraints: Determine the conditions

Fig. 8 The XP Release Cycle

 Extreme Programming Practices Incremental planning: Requirements are recorded on Story Cards and the Stories to be included in a release are determined by the time available and their relative priority. The developers break these stories into development "Tasks". Small Releases: The minimal useful set of functionality that provides business value is developed first. Releases of the system are frequent and incrementally add functionality to the first release.

IJCSI International Journal of Computer Science Issues, Vol. 7, Issue 5, September 2010 ISSN (Online): 1694-0814


Simple Design: Enough design is carried out to meet the current requirements and no more. Test first development: An automated unit test framework is used to write tests for a new piece of functionality before functionality itself is implemented. Refactoring: All developers are expected to re-factor the code continuously as soon as possible code improvements are found. This keeps the code simple and maintainable. Pair Programming: Developers work in pairs, checking each other’s work and providing support to do a good job. Collective Ownership: The pairs of developers work on all areas of the system, so that no islands of expertise develop and all the developers own all the code. Anyone can change anything. Continuous Integration: As soon as work on a task is complete, it is integrated into the whole system. After any such integration, all the unit tests in the system must pass. Sustainable pace: Large amounts of over-time are not considered acceptable as the net effect is often to reduce code quality and medium term productivity. On-site Customer: A representative of the end-user of the system (the Customer) should be available full time for the use of the XP team. In an extreme programming process, the customer is a member of the development team and is responsible for bringing system requirements to the team for implementation.  1. 2. 3. XP and agile principles Incremental development is supported through small, frequent system releases. Customer involvement means full-time customer engagement with the team. People not process through pair programming, collective ownership and a process that avoids long working hours. Change supported through regular system releases. Maintaining simplicity through constant refactoring of code [1]. Advantages Lightweight methods suit small-medium size projects. Produces good team cohesion. Emphasises final product. Iterative. Test based approach to requirements and quality assurance. Disadvantages Difficult to scale up to large projects where documentation is essential. Needs experience and skill if not to degenerate into code-and-fix. Programming pairs is costly.


Test case construction is a difficult and specialized skill [6].

4. Conclusion and Future Work
After completing this research , it is concluded that : 1. There are many existing models for developing systems for different sizes of projects and requirements. 2. These models were established between 1970 and 1999. 3. Waterfall model and spiral model are used commonly in developing systems. 4. Each model has advantages and disadvantages for the development of systems , so each model tries to eliminate the disadvantages of the previous model Finally, some topics can be suggested for future works: 1. Suggesting a model to simulate advantages that are found in different models to software process management. Making a comparison between the suggested model and the previous software processes management models. Applying the suggested model to many projects to ensure of its suitability and documentation to explain its mechanical work.



[1] Ian Sommerville, "Software Engineering", Addison Wesley, 7th edition, 2004. [2] CTG. MFA – 003, "A Survey of System Development Process Models", Models for Action Project: Developing Practical Approaches to Electronic Records Management and Preservation, Center for Technology in Government University at Albany / Suny,1998 . [3] Steve Easterbrook, "Software Lifecycles", University of Toronto Department of Computer Science, 2001. [4] National Instruments Corporation, "Lifecycle Models", 2006 , [5] JJ Kuhl, "Project Lifecycle Models: How They Differ and When to Use Them",2002 [6] Karlm, "Software Lifecycle Models', KTH,2006 . [7] Rlewallen, "Software Development Life Cycle Models", 2005 , [8] Barry Boehm, "Spiral Development: Experience, Principles, and Refinements", edited by Wilfred J. Hansen, 2000 .
Nabil Mohammed Ali Munassar was born in Jeddah, Saudi Arabia in 1978. He studied Computer Science at University of Science and Technology, Yemen from 1997 to 2001. In 2001 he

4. 5.  1. 2. 3. 4. 5.  1. 2. 3.

IJCSI International Journal of Computer Science Issues, Vol. 7, Issue 5, September 2010 ISSN (Online): 1694-0814 received the Bachelor degree. He studied Master of Information Technology at Arab Academic, Yemen, from 2004 to 2007. Now rd he Ph.D. Student 3 year of CSE at Jawaharlal Nehru Technological University (JNTU), Hyderabad, A. P., India. He is working as Associate Professor in Computer Science & Engineering College in University Of Science and Technology, Yemen. His area of interest include Software Engineering, System Analysis and Design, Databases and Object Oriented Technologies. Dr.A.Govardhan: received Ph.D. degree in Computer Science and Engineering from Jawaharlal Nehru Technological University in 2003, M.Tech. from Jawaharlal Nehru University in 1994 and B.E. from Osmania University in 1992. He is Working as a Principal of Jawaharlal Nehru Technological University, Jagitial. He has published around 108 papers in various national and international Journals/conferences. His research of interest includes Databases, Data Warehousing & Mining, Information Retrieval, Computer Networks, Image Processing, Software Engineering, Search Engines and Object Oriented Technologies.


Similar Documents

Premium Essay


...Principle of Software Engineering Table of Contents Abstract 3 Introduction 4 Boehm's First Law 4 Boehm's Second law 5 Conway's law 5 Parnas Law 6 Corbató Law 7 Observation 8 Theory 9 Law 9 Question 3 10 Law 11 References 12 Abstract The purpose of the study is to show the capability to understand the set of laws that are the part of principles of the software engineering. In this paper, it is discussed that there are many laws related to the software engineering but only few of them are to be addressed. Boehm first and second law, Conway’s laws, Parnas laws & Corbato law were discussed with examples. There are two relationship processes that are also discussed, related to the software Engineering. Law method and tools which are depended on each other and they are performing the task with the help of principle and process by following the rules. Same scenario is followed in other relation too, where observation, law and theory are depended on each other. Observation is repeatable to law and law is explained by theory. Theory should be confirmed by the law and it predict by the observation before further proceeding. Introduction Question No 1 Boehm's First Law Errors are more regular in the middle of fundamentals and configuration exercises and are more abundant when they are displaced. In this law, some basic configuration errors do outnumber code blunders. However, cost stays......

Words: 1641 - Pages: 7

Free Essay


...Identify two periodical publications that focus on software architecture (either solely or partly). Submit the following information: publication name, URL, publisher name, & the year it was first published. IEEE Potentials, First Publication Year: 1982 URL : Publisher Name: IEEE Xplore Msdn magazine First Publication Year: 2001 URL: Publisher Name: The Microsoft journal for developers Write a half-page short essay comparing and contrasting software architects and software engineers. Software architect has responsibility for guaranteeing coherence of all aspects of the project as an integrated system. Architect answerable for overall technical quality, developer for lower implementation selections. The architect holds the futuristic views and proactively sees the system before it\'s designed, being the holder of the vision. Software architect focuses on money and also the disposition and drive to guide individuals. a leader who will apply/share their broad framework. Pragmatic handling of the technical solution and act with the business in addition as the techies, marketing the vision to each. A software architect has the vision to own the most effective style ideas. Architects will see each micro and macro (inwards and outward) whereas engineers see small and outwards and want to be carried by the architect to examine macro/outwards. Maintaining...

Words: 892 - Pages: 4

Premium Essay


...Software Quality Assurance Software quality assurance Software quality assurance, often referred to in the industry as "software testing" or "QA testing" consists of thoroughly testing every aspect of a software project to ensure that: 1. It functions as intended and does not contain errors 2. It complies with the previously established development guidelines As the interactive software industry grows, software quality assurance has become more and more complicated. Many offshoots have arisen and considerably complicated the software testing jargon: security testing, unit testing, usability testing, load testing, scripted testing, compatibility testing, etc. In the end, what software quality assurance is all about is making sure that your software product works seamlessly for all your users. While we may expand into other areas in the future, we at the Crowdsourced Testing company specialize in one particular type of testing known as functional testing. The sad reality of software quality assurance The unfortunate reality of the software development industry is that testing is often neglected because development companies are under a tremendous amount of pressure to deliver their projects faster and faster. Furthermore, software programming is a complex endeavor and it is very difficult to know ahead of time exactly how much time will be needed to develop a particular project. What usually ends up happening is that programmers work until the very last minute......

Words: 616 - Pages: 3

Free Essay


...Robert P. Ward Software Engineering in the Small Smaller-sized software companies are developing significant products that need effective, tailored software engineering practices. n 1968, the NATO Software Engineering Conference in Garmisch, Germany [6] initiated the concept of software engineering, identifying the problems with producing large, high-quality software applications. In 1975, De Remer [2] introduced the terms, “programming in the small” and “programming in the large” to differentiate the development characteristics of large-scale software development from detailed programming (for example, data structures and algorithms). The principal source of large-scale software at the time was development contracts issued by the U.S. Department of Defense. Since then, virtually all software engineering literature has concentrated explicitly and implicitly on the model of DoD contract software development. Since the late 1970s, the microcomputer revolution has dramatically increased the quantity of software produced, the average I size of programs, and the number of companies involved in software development. Much more software is produced for internal use, commercial applications, and the mass-market than for deep-pocketed government and large industry. Using the number of units sold, mass-market software dwarfs the other forms of software sales. The growth of the software industry has produced many small companies that do not do contract software, but rather......

Words: 2136 - Pages: 9

Free Essay


...Ariel M. Vasquez November 24, 2014 CIS331 System Modeling Theory Professor Randy Arvay Software System Architecture For this case the question is asked which system would be best to implement for this case. There are several different types of cases to chose from. They all with their own particular benefits and negatives at the same time The one that fits this needs in particular would be the event driven system. What is an event driven architecture system? An event driven architecture, or EDA for short, is a pattern that focuses on promoting production, detection, and consumption. Most of its works occur during an event. In the medical field, which this case revolves around, have thing change a lot during the course of not only a day even within every hour this change. Whether it's from a patient's medical records, stock of inventory, medicines provided to a patient, and even when a patient enters and exits the hospital. With a system like EDA thing will only occur when things change and this pattern seems to be able to handle those changes better than the others. The following image will show basically how this type of system will work. A system that integrates EDA may also provide a higher level of service to help with the implementation of EDA. Things like security, reliable messaging, content based routing, and mapping and transformation. The security that this provides is message encryption, authentication, and access control. With the messaging this......

Words: 418 - Pages: 2

Premium Essay


...Software is a general term for the various kinds of programs used to operate computers and related devices. (The term hardware describes the physical aspects of computers and related devices.) Importance of Software Security Assurance As organizations worldwide increase their reliance on software controls to protect their computing environments and data, the topic of Software Security Assurance grows in importance. The tremendous potential costs associated with security incidents, the emergence of increasingly complex regulations, and the continued operational costs associated with staying up to date with security patches all require that organizations give careful consideration to how they address software security. For more information on Software Security Assurance, see Wikipedia on Software Security Assurance. Oracle Software Security Assurance Encompassing every phase of the product development lifecycle, Oracle Software Security Assurance (OSSA) is Oracle's methodology for building security into the design, build, testing, and maintenance of its products. Oracle's goal is to ensure that Oracle's products, as well as the customer systems that leverage those products, remain as secure as possible. Oracle Software Security Assurance is a set of industry-leading standards, technologies, and practices aimed at: • Fostering security innovations. Oracle has a long tradition of security innovations. Today this legacy continues with Oracle's market leading database......

Words: 484 - Pages: 2

Free Essay

Hardware and Software

...Hardware and Software Paper CIS 205 Hardware and software play a very important role in business today and if combined together they can support personal, workgroup, and enterprise computing. In my organization we use Windows based computers for each workstation in each respective location. With the appropriate hardware networking the computers together, we are able to communicate through our network. In this case, we are a small business so we followed the steps necessary to map drives together in the various locations. The hardware needed for our network is a modem, router, Ethernet cables, external hard drives, and power supplies. The software we use to run our network is Windows. When used together this hardware and software help us operate our organization efficiently by easily sending and receiving information. We are able to navigate to any computer’s information in our company through this network. As a design, printing, and embroidery company, we use many online applications to help support and organize our information. The majority of our incoming business comes from the internet. I use an online application called Oss designer to download customer art, organize customers data, and obtain the necessary information from a customer to get the job done. We also use the Oss software to obtain payments for our services. In order to track customers we use an invoice and customer tracking program called Quickbooks. This software enables us to easily create......

Words: 572 - Pages: 3

Free Essay

Hardware Software

...HARDWARE AND SOFTWARE PAPER Hardware and Software Paper Nathen Hill University of Phoenix Introduction Here at D & G Inc. we are a shipping and receiving company. We sell just about everything, we are a middle man company for several online stores. When you purchase a products online like a DVD the company you purchase through invoices D & G Inc. and we ship the product via UPS to you. At D & G Inc. the Hardware we use a basic Dell Computers running Windows XP. We have about thirty computers in the warehouse and offices. We use Telzall scanning devices to scan and keep track of all merchandise in the warehouse. Without the proper hardware and software tools, the job of keeping track of tens of thousands of products would be a much more time consuming, and need many more employees to accomplish correctly . Hardware and Software The software we use here at D & G Inc. is the most important part of smooth operations. The software we use was created for us at D & G Inc. The system is called SMART it connects all of our databases together. The SMART system makes easy access to any database through, one of the dell computers or through the handheld Telzall scanners. The SMART system runs the time clocks to keep track of all employee hours. First you scan in your ID badge in to the time clock provided on the wall next to all exits. Once you are scanned in to the SMART system you are allowed to log in to the......

Words: 708 - Pages: 3

Free Essay

Escoger Un Software

...calendario para una presentación del software * Reunir a todo el equipo para la presentación del software. * Seleccionar 2 candidatos posibles. * Elegir el proveedor adecuado. Primero debemos recolectar la información de los posibles proveedores y de entre ellos escoger los 3 o 5 proveedores que se ajusten más a nuestros requerimientos. Después debemos reunirnos con cada uno de ellos para poder conversar y evaluar si pueden ser posible candidatos a para convertirse nuestro proveedor. Una vez que nos hemos reunidos pasamos a agendar una presentación del software con todos los empleados que van a utilizar el mismo para que se vayan familiarizando con este. Una vez que hayamos realizado el análisis del posible proveedor y lo hayamos escogido, pasamos a la firma del contrato con el proveedor bajo los términos y condiciones pactadas entre las partes. * Proporcionar información para la personalización de aplicaciones de gestión. Debemos proporcionar cualquier información útil para el equipo: manual de políticas y procedimientos, informes clave, el acceso al sistema actual y para que de esta forma el proveedor sea más exacto con el software que vamos a usar para operar nuestra empresa. * Análisis y la firma del documento DERCA. Este documento es donde especificaremos los requerimientos de nuestra empresa como los procesos del sistema, las interfaces de entrada y los conectores de salida, como tomamos la decisión de usar un canned software tenemos...

Words: 1063 - Pages: 5

Premium Essay


... Chinyere repper. Software for Business. MS PROJECT (PROJECT PLANNING) Microsoft Project is a project management software program, developed and sold by Microsoft, which is designed to assist a project manager in developing a plan, assigning resources to tasks, tracking progress, managing the budget, and analyzing workloads. Microsoft Project was the company's third Microsoft Windows-based application, and within a couple of years of its introduction it became the dominant PC-based project management software. While part of the Microsoft Office family, it has never been included in any of the Office suites. It is available currently in two editions, Standard and Professional. Microsoft Project's proprietary file format is mpp. Microsoft Project and Microsoft Project Server are the cornerstones of the Microsoft Office Enterprise Project Management (EPM) product. Microsoft Project 2010 features the Ribbon user interface. Microsoft Project management software is closely integrated with Microsoft Office suite and also includes a Client Access License (CAL) that allows easy connection with Office Project Server. It is a project management software that is mainly used to create plans, monitor progress, analyze workloads, designate resources to tasks and manage budgets. The software also helps in establishing critical path schedules and may also be......

Words: 841 - Pages: 4

Free Essay

Hardware and Software

...Hardware and Software Name Professor Name Name of Class Hardware and Software Here at Enterprises we are a shipping and receiving company. We sell just about everything; we are a middleman company for several online stores. When you purchase products online like a DVD the company you purchase through invoices Enterprises and we ship the product via UPS to you. At Enterprises the Hardware we use a basic Dell Computers running Windows XP. We have about thirty computers in the warehouse and offices. We use Telzall scanning devices to scan and keep track of all merchandise in the warehouse. Without the proper hardware and software tools, the job of keeping track of tens of thousands of products would be a much more time consuming, and need many more employees to accomplish correctly. Hardware and Software The software we use here at D & G Enterprises is the most important part of smooth operations. The software we use was created for us at Enterprises. The system is called SMART it connects all of our databases together. The SMART system makes easy access to any database through, one of the dell computers or through the handheld Telzall scanners. The SMART system runs the time clocks to keep track of all employee hours. First you scan in your ID badge in to the time clock provided on the wall next to all exits. Once you are scanned in to the SMART system you are allowed to log in to the database and access information you need to perform......

Words: 698 - Pages: 3

Free Essay

Hardware and Software

...Hardware and Software Your Name Date Class Name Teacher’s name The system that best resembles the hardware and software used at the nursing home located in PA that I used to work for is the Power Macintosh 9500. According to, the system was sold between 1995 through 1997 and has the following hardware installed, “It was powered by a PowerPC 604processor, a second-generation PowerPC chip which was faster than the earlier PowerPC 601 chip. The 180MP and 200 used the enhanced PowerPC 604e processor. The CPU was connected via a daughterboard, and so could be swapped easily. Available were single-processor cards ranging from 120 to 200 MHz, and a dual processor card with two 180 MHz CPUs. It was the first Macintosh to use the PCI standard, with six PCI slots available, with one always needed for the graphics card.” The exact breakdown of system hardware can be seen at the Apple website at the following link, The overall operations of the system are great for its age and can even be enhanced with a new program entitled “Leopard” (also available from Apple) that could help the overall performance of the system and was actually the oldest model that is compatible with that program. As for the software, we all know that there are significant differences between workgroup, personal, and enterprise uses such differences can be seen with the different programs each use has to offer, some examples of the differences are......

Words: 847 - Pages: 4

Premium Essay

Software Licence


Words: 6081 - Pages: 25

Premium Essay

Software Testing

...ISSN 0974-2174, Volume 7, Number 5 (2014), pp. 463-474 © International Research Publication House A Review of Software Testing Techniques Manpreet Kaur1 and Rupinder Singh2 1 Department of CSE CGC, Gharuan Mohali, India 2 CSE CGC, Gharuan Mohali, India Abstract Software testing is important to reduce errors, maintenance and overall software costs. One of the major problems in software testing area is how to get a suitable set of test cases to test a software system. We identify a number of concepts that every software engineering student and faculty should have learned. There are now many testing techniques available for generating test cases. This set should ensure maximum effectiveness with the least possible number of test cases. The main goal of this paper is to analysed and compare the testing technique to find out the best one to find out the error from the software. Keywords: Software testing; process model; testing techniques; 1. Introduction Software testing is a process or a series of processes designed to verify computer code does what it was designed to do. According to ANSI/IEEE 1059 standard [1, 2], Testing can be defined as ―A process of analyzing a software item to detect the differences between existing and required conditions (that is defects/errors/bugs) and to evaluate the features of the software item. Another more appropriate definition is this: [3] Testing is the process of executing a program with the intent of finding......

Words: 4928 - Pages: 20

Premium Essay

Application Software

...Applications Software The three primary features commonly used applications software that will be summarized in this paper are personal application software, workgroup application software, and enterprise application software. Personal Application Software’s 1) Word processing; helps create, edit and print text documents. I.e., Microsoft word, Corel WordPerfect, Google Docs, Apple Pages and Sun Writer. 2) Spreadsheet; provides a wide range of built-in functions for statistical, financial, logical, database, graphics, and date and time calculations. I.e., Microsoft Excel, IBM Lotus 1-2-3, Google Spreadsheet, Apple Numbers and Sun Calc. 3) Database; stores, manipulate, and retrieve data. I.e., Microsoft Access, IBM Lotus Approach, Borland dBASE, and Sun Base. 4) Graphics; develop graphs, illustrations, and drawings. I.e., Adobe Illustrator and Adobe FreeHand. 5) Project management; plans, schedule, allocate, and control people and resources needed to complete a project according to schedule. 6) Financial management; provides income and expense tracking and reporting to monitor and plan budgets. I.e., Intuit Quicken. 7) Desktop publishing; use with personal computers and high-resolution printers to create high-quality printed output, including text and graphics, various styles of pages can be laid out; art and text files from other programs can also be integrated into published pages. I.e., Quark Xpress, Microsoft Publisher, Adobe PageMaker,...

Words: 392 - Pages: 2