...COMMUNICATION MEI 2015 CDAD2103 METHODOLOGY OF INFORMATION SYSTEM DEVELOPMENT Contents 1.1 Introduction 1 1.2 Methodology 1 1.3 Types of Software developing life cycles (SDLC) 2 1. Waterfall Model 2 2. V-Shaped Model 4 3. Evolutionary Prototyping Model 5 4. Spiral Method (SDM) 7 5. Iterative and Incremental Method 8 6. Extreme programming (Agile development) 10 1.4 CASE (computer-aided software engineering) 11 1.5 Conclusion 16 Introduction System development methodology is a standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems. Organizations use a standard set of steps, called system development methodology to develop and support their information systems. Like many processes, the development of information systems often follows a life cycle. For example, a commercial product such as a Nike sneaker or a Honda car follows a life cycle; it is created, tested and introduced to the market. Its sales increase, peak and decline. Finally, the product is removed from the market and is replaced with something else. Many options exist for developing information systems, but the most common methodology for system development in many organizations is system development life cycle. However, it is important to know other alternative development methodology available in order to maximize the development process. there are four important...
Words: 2577 - Pages: 11
...Individual Assignment The two software development methodologies that I have selected for this assignment are the Waterfall Model (as chosen by you) and the Spiral model (chosen by me). These two methods often cause confusion amongst software developers as they are unable to decide which of the two is better for the software they are developing. The first software model to be used was the waterfall. The spiral, that came later, is one of the most popular models in the field of software development. I will go further into each of the above mentioned two models after I describe the four laws given in the prescribed text. I will start with the Glass Law (dubbed law 1). If I was to describe the Glass law, I would say in a nutshell, requirements are the foundation of any project, and incomplete or misinterpreted or misjudged requirements are the key to failure. What I mean by the above is that when the requirements are not clarified, incomplete, unstable or far too many to cope with, the project will face a high chance of failure. A real world example, which added approximately $560M USD to the cost of the airport and became a modern era example of Glass law, was originally planned to automate the handling of baggage through the entire airport, but due to underestimation of complexity, changes in requirements, underestimation of schedule and budget and other causes was a drastic failure. Moving to Boehm’s laws, the first and second law complement each...
Words: 1378 - Pages: 6
...SOFTWARE DEVELOPMENT: 1. Introduction Computers are becoming a key element in our daily lives. Slowly and surely they are taking over many of the functions that effect our lives critically. They are now controlling all forms of monetary transactions, manufacturing, transportation, communication, defence systems, process control systems, and so on. In the near future, they will be found in our homes, controlling all forms of appliances. Left to themselves, they are harmless pieces of hardware. Load the right kind of software, they can take you to the moon, both literally and figuratively. It is the software that gives life to them.When they are going to play such a crucial role, one small flaw either in the hardware or the software can lead to catastrophic consequences. The sad part is, while there are well defined processes based on theoretical foundations to ensure the reliability of the hardware, same thing can not be said about software. There is no theory for software devlopment as yet. But at the same time, it is mandatory that software always behaves in a predictable manner, even in unforeseen circumstances. Hence there is a need to control its development through a well defined and systematic process. The old fashioned 'code & test' approach will not do any more. It may be good enough for 'toy' problems, but in real life, software is expected to solve enormously complex problems. Some of the aspects of real life software projects are: Team effort: Any large...
Words: 3162 - Pages: 13
...Chapter 3 – Conceptual Design: An Overview of Methodologies, Models and Notations CHAPTER OBJECTIVES (YOU SHOULD BE ABLE TO): 1. Define and describe a methodology. 2. Define and describe traditional, structured analysis & design, information modeling, and object-oriented methodology classifications. 3. Define and describe a Data Flow Diagram (DFD) and an Entity-Relationship Diagram (ERD). 4. Define and describe attributes, operations and relationships in an object-oriented methodology. 5. Define and describe the foundational characteristics of an object-oriented methodology. 6. Describe two classic information systems development challenges and their potential resolution. 7. Discuss Classification Theory and its relationship with object-oriented methodologies. 8. Describe Rational Corporation's Unified Software Development Process. 9. Define parallelism, substitution and omission. 10. Describe the Unified Modeling Language (UML) and describe Use Case, Class Diagram and Interaction Diagram. 11. Describe a simplistic object-oriented methodology for applying and using the UML. 12. Describe the foundational characteristics of the UML’s Class Diagram DESIGN A generic systems development life cycle (SDLC) was presented in an earlier chapter. You may recall that the purpose for this version of a SDLC was to give you a simplified way of sequentially studying the activities that are utilized to produce software-intensive information systems. In reality the SDLC...
Words: 13243 - Pages: 53
...IntroductIon to AgIle SoftwAre development June 2007 tAble of contentS Executive summary............................................................................................................................................................ 3 Agile vs. waterfall: practical differences in methodology .............................................................. 4 Two agile software development methodologies ................................................................................. 6 Xp ......................................................................................................................................................................................................... 6 The XP development process ....................................................................................................................................................... 6 XP rules and concepts ......................................................................................................................................................................7 Scrum ................................................................................................................................................................................................. 8 Scrum management........................................................................................................................................................................ 8 Scrum development ................
Words: 2845 - Pages: 12
...do with their technology. The system development life cycle is a powerful mechanism for evaluating an organization's current and future SDLC needs (Norton, 2012). IT methodologies lay the blue print for being able to manage and accomplish projects when developing an organization’s needs. Traditional methodology and agile methodology are methodologies used. Traditional Methodology One example of traditional methodology is the waterfall approach. The waterfall follows the belief that all user requirements needed for the design can be collected upfront. This is referred to method makes the assumption that all requirements can be gathered up front during the requirements phase (Hughey, 2009). During this approach, the project manager tries their best to establish the user requirements. Once the user requirements are obtained the process starts. This process is known as downhill. The process goes through four phases. They are design, implementation, verification, and maintenance. To starts the design phase, an analysis is done to break the design in sub-phases logical design and physical design. During the Logical Design phase, the system's analysts makes use of the information collected in the Requirements phase to design the system independently of any hardware or software system (Hughey, 2009). Once the logical design has been complete, the physical design begins to surface. The physical design determines the specific software and hardware needed for the design. ...
Words: 1031 - Pages: 5
...Pearson Case Analysis I. Executive Summary: Pearson’s Digital Learning Division’s Vice President of Product Management, Greg Adams-Woodford, is beginning to feel the growing pains of a new product development process that he launched after joining the organization one-year ago. The process transformation from a “Waterfall” to “Aigle” methodology was introduced as a means to tackle a disconnect between what the customer wants and what the software developers are producing. As Adams-Woodford works to develop a product road map, he is faced with three critical decisions: 1. Move from one form of the Aigle process (Scrum) to a newer process (Kanban), 2. Extend the Aigle methodology to other teams within the business unit, and 3. Expand Aigle to other teams outside of the business unit in the organization at large. Recommendations for Adam-Woodford are as follows: * Meet with a software development product managers and other key influencers within the business function to analyze, evaluate, and decide to move forward with a Scrum or Kanban process, * After a sufficient Aiglie problem resolution with the software development group, Adam-Woodford should expand Aigle to other teams within the business unit deemed appropriate, * And postpone extending the Aigle process to other Pearson business units in order to focus on the current, more urgent needs, within his product management scope. II. Problem: How can the VP within the Digital Learning Division of the North American...
Words: 1428 - Pages: 6
...There is no IT meeting that does not talk and debate endlessly about Waterfall vs. Agile development methodologies. Feelings run strong on the subject with many considering Agile ‘so of the moment’, just so right, while Waterfall is thought to be passé! But, before deciding which is more appropriate, it is essentially important to provide a little background on both. Waterfall A classically linear and sequential approach to software design and systems development, each waterfall stage is assigned to a separate team to ensure greater project and deadline control, important for on-time project delivery. A linear approach means a stage by stage approach for product building, e.g. 1. The project team first analyses, then determining and prioritising business requirements / needs. 2. Next, in the design phase business requirements are translated into IT solutions, and a decision taken about which underlying technology i.e. COBOL, Java or Visual Basic, etc. etc. is to be used. 3. Once processes are defined and online layouts built, code implementation takes place. 4. The next stage of data conversion evolves into a fully tested solution for implementation and testing for evaluation by the end-user. 5. The last and final stage involves evaluation and maintenance, with the latter ensuring everything runs smoothly. However, in case a glitch should result, changing the software is not only a practical impossibility, but means one has to go right back to the beginning...
Words: 3187 - Pages: 13
...2012 Waterfall vs. Agile Methodology Mike McCormick MPCS, Inc. Revised Edition 8/9/2012 Waterfall vs. Agile Methodology Contents Waterfall vs. Agile Model Comparison .........................................................................................3 Conceptual Difference.................................................................................................................3 Efficiency ....................................................................................................................................4 Suitability ....................................................................................................................................4 Waterfall Model Diagram .............................................................................................................5 Explanation of the Waterfall Model ..............................................................................................5 Phase I: Requirements................................................................................................................6 Phase II: Analysis .......................................................................................................................6 Phase III: Design.........................................................................................................................6 Phase IV: Coding ....................................................................................................
Words: 3023 - Pages: 13
...courses at the various and numerous campuses which are located across the Midwestern United States. As a result any development methodology would need to take into consideration the system requirements and how these can best be implemented. Although various options are available for the development methodology the two recommendations are for either a Scrum-based approach (agile) or a plan-based approach (waterfall). Each approach is significantly different in terms of the way in which the project will be managed and developed, and the relative differences as well as an analysis of the specific details for each approach are detailed below: Scrum Methodology As this is an agile methodology, the key emphasis is on a series of rapid development cycles which are linked between the overall requirements for the final system. Such cycles are usually completed within 30 days, and will be initiated from a high level plan which is amended on a regular basis throughout the development. Each developer is afforded a great degree of control in terms of directing the development in the most appropriate manner: • Product Backlog – the product specifications are used to create alist of items. • Sprint Backlog – the list of tasks that should be completed in the next sprint and is prone to frequent changes. • Sprint – the development period which manipulates the backlog into a software implementation. • Daily Scrum – communication based meetings where developers and project members outline tasks...
Words: 753 - Pages: 4
...Chapter One 1.1 With what other terminology is systems analysis and design synonymous? Systems analysis and design is also known as information systems engineering, software engineering, systems engineering, software development, and systems development. 1.2 What activities and deliverables are included in analysis? Activities: systems planning, feasibility study (optional), requirements determination, user acceptance,and prototyping (optional). Deliverables: Requirements specification and prototype (optional). 1.3 What activities and deliverables are included in design and implementation? Activities: Physical design, prototyping (optional), software construction/purchase, user documentation, testing, training, user acceptance, conversion, and implementing the system. Deliverable: Information system. 1.4 Describe a system and the components of a systems model. A generic systems model consists of six components- inputs, processes, outputs, controls, feedback, and boundary. Using predetermined controls, a system accepts inputs at its boundary, processes them into outputs, and provides a feedback mechanism for taking any necessary corrective action. 1.5 What two key components distinguish an information system from an automated information system? Software and hardware. 1.6 How are data incorporated into an automated information system and what role does it play? Data are either input, stored, or output. As part of the information system,...
Words: 9128 - Pages: 37
...Month, Year DECLARATION I hereby declare that the entire thesis work entitled, “……………..” submitted to the department of Information and Communication Technology, Garden City University College, in fulfilment of the requirement for the award of the degree of BSc Computer Science, is a bonafide record of my own work carried out under the supervision of Mr/Mrs/Ms . ……….. I further declare that the thesis either in part or full, has not been submitted earlier by me or others for the award of any degree in any University. ACKNOWLEDGEMENTS This section contains expressions of gratitude to advisor(s) and anyone who helped you: 1. technically (including materials, supplies) 2. intellectually (assistance, advice) 3. financially (for example, departmental support, travel grants) ABSTRACT The abstract is an important component of your thesis. Presented at the beginning of the thesis, it is likely the first substantive description of your work read by an external examiner. The abstract is the last section to write. An abstract is not merely an introduction in the sense of a preface, preamble, or advance organizer that prepares the reader for the thesis. In addition to that function, it must be capable of substituting for the whole thesis when there is insufficient time and space for the full text. To preserve visual coherence, you may wish to limit the abstract for your doctoral dissertation to one double-spaced page. Points to note: Length should be ~ 1-2 paragraphs, approx...
Words: 2039 - Pages: 9
...Agile vs. Prescriptive Processes CS5704 - Assignment 1 Jitrat Jaidee jaideej@hotmail.com AGILE SOFTWARE DEVELOPMENT Agile Development is one of the methodologies use in software engineering to help develops software. Today, there are a lot of different approach to Agile method. However, they all share the same value and principals. This method is value interactions over team and customer, workable software, and adaptable to change. Over the processes, documentation, contract, and plan. Agile developer also following 12 principle. 1, Their first priority is to delivery fast and quality software that will satisfy customer. 2, be adaptable to any change in requirement at any point in time, Agile development always welcome change. 3, frequency deliver working software between a few week to a few month. 4, daily interaction between developer and customer. 5, The project built around individuals motivation. give them what they need and trusted that they will get the job done. 6, The best way to relay an information is live(face to face) conversation. 7, Using the working software as the main measurement of progress. 8, The process in agile environment is going in stable pace. 9, through out the processes, always attention to technique and design, in order to improve agility. 10, Keep the progress simplicity. 11, The self Organize team will naturally produce good architectures, requirements, and designs. 12, Often during progress Agile team hold a regular...
Words: 756 - Pages: 4
...Staffordshire University & APIIT-UCTI Masters Level Case Study Date Assigned : Fri, 05-Mar-2010 Date Due : Wed, 02-Jun-2010 (before 7pm) Lecturer : Dhason Padmakumar ________________________________________________________________________ 1. Your Task • The Chief Executive officer of your organization has instructed you to create a Project Management Procedural Handbook in preparation for a series of possible software development projects that your organization is about to undertake. The handbook will be used as a guide/template for the management of projects. It should be approximately 2500 words long • The content of the handbook should be of: ▪ Practical use to you and your workplace colleagues. ▪ Ensure that your organisation’s projects are conducted with the most appropriate tools and methods to the highest possible standards. ▪ Demonstrate academic rigour based around the structure of this module and the further research that you perform. 2. The Handbook Itself • It follows that the Handbook must be of a professional standard. • To help you achieve this a suggested template has been attached as a guide for the Handbook structure. Please feel free to add or remove sections for your own handbook scenario. • You must ensure that you identify and reference the work of others. Therefore, provide...
Words: 1378 - Pages: 6
...Introduction The core of Information Systems (IS) has long been suggested to be software engineering. Software Engineering Research Methodology (SERM) can be known as an approach that mixed a galaxy of new concepts and emerging information technologies and then express this mixture in an innovative artefact in order to do some academic knowledge to basic research field and prompt the further research in the relevant fields. There need to construct a paradigm that can completely describes research using SERM approaches. A SERM framework based on this paradigm is presented to allow developmental research to be performed using a stringent methodology. Software Engineering as Research Research can be described as a scientific approach rather than one of the several different ways of promoting building and understanding of new knowledge. Moreover, scientific research is defined as a process of systemic inquiry conducted with the protection of a theoretical infrastructure. Research and evaluation, which is similar to research, can be distinguished by using theory as the fundamental. As Mertens argues that evaluation is associated with the acquiring of information for decision making in a given environment, however, research, which means a wider field, is more typically connected with contributing new knowledge that can be used in the relative fields Can software engineering be research? According to the definitions from Sir Karl Popper (1980) and Blake (1978), whether or...
Words: 846 - Pages: 4
