Reference no: EM131158971
The field of SE has matured in the last 45 years, and practitioners have learned many ways to sustain prediction, product, processes, and resource improvements. Over the years, some SE practices have been outdated but most still relevant and highly applicable. Quality measures must be proven in advance for widely implementation, and for this reason, textbooks and SE articles offer guidelines for evaluating current situations and identifying opportunities for improvement. The readings in this module provide the SE definition and how IT professionals learn and gain experience in SE.
Software engineering consists of several activities that co-exist together for a successful project. These activities are known for the 4P's, people, product, project, and process. Developing a software project without a framework or methodology is risky and less likely to succeed. The 4P's in combination provide the basis for SE, a discipline that has been tested over time. Module 1 introduces several methodologies from the perspective of methods and principles used in the sub-discipline of software design.
Read Conger's Chapter 1 and Chapter 2 (pages 36-50). Please note that Sue Conger's textbook is 46.59 MB. Allow a few minutes to download from the Global Text Project size. Since the textbook is covered under the Creative Commons Attribution 3.0 License, you can safely download and save it in your computer for future use.
Conger, S. (2008). The New Software Engineer. Belmont, CA: Wadsworth Publishing Company [Global Text]. Retrieved from http://dl.dropbox.com/u/31779972/The%20New%20Software%20Engineering.pdf
Glass, R (2002). An early history of software engineering. Retrieved from http://www.cs.colorado.edu/~kena/classes/5828/s99/comments/srinivasan/01-29-1999.html
IEEE Standard Board. (1990). IEEE Standard glossary of software engineering terminology. Retrieved from http://dis.unal.edu.co/~icasta/GGP/_Ver_2012_1/Documentos/Normas/610-12-1990.pdf
Requirements Engineering Qualification Board. (2011). Standard glossary of software engineering terminology. Retrieved from http://en.gasq.org/fileadmin/user_upload/redaktion/en/Data/REQB_Standard_glossary_of_terms_used_in_Requirements_Engineering_1.0.pdf
After reading the course materials, please write a 3- to 4-page paper answering the following.
Define how each software development methodology's history is affected by technology.
Describe some area of your organization that could use an application to speed its work, make its work more accurate, enhance jobs, provide better information to worker or simplify work life. Describe the application and how it would meet its goals. What methodology is best suited for your application and why?
Assignment Expectations (50 points total)
Length: Minimum 3-4 pages excluding cover page and references (since a page is about 300 words, this is approximately 900-1,200 words).
APA formatted references and proper citations a must.