ELABORATION Productivity Plan and Document vs Agile lifecycles Productivity is

Elaboration productivity plan and document vs agile

This preview shows page 58 - 61 out of 517 pages.

ELABORATION: Productivity: Plan-and-Document vs. Agile lifecycles Productivity is measured in the engineer-hours to implement a new function. The difference is the cycles are much longer in Waterfall and Spiral vs. Agile—on the order of 6 to 24 months vs. 1/2 month—so much more work is done between releases that the customer sees, and hence the chances are greater that more work will ultimately be rejected by the customer. 1.10 Guided Tour of the Book I hear and I forget. I see and I remember. I do and I understand. Confucius
Image of page 58
With this introduction behind us, we can now explain what follows and what paths you might want to take. To do and understand, as Confucius advises, begin by reading Appendix A . It explains how to obtain and use the “bookware,” which is our name for the software associated with the book. The rest of the book is divided into two parts. Part I explains Software as a Service, and Part II explains modern software development, with a heavy emphasis on Agile. Figure 1.9: An iteration of the Agile software lifecycle and its relationship to the chapters in this book. The dashed arrows indicate a more tangential relationship between the steps of an iteration, while the solid arrows indicate the typical flow. As mentioned earlier, the
Image of page 59
Agile process applies equally well to existing legacy applications and new applications, although the customer may play a smaller role with legacy apps. Chapter 2 starts Part I with an explanation of the architecture of a SaaS application, using an altitude analogy of going from the 100,000-foot view to the 500-foot view. During the descent you’ll learn the definition of many acronyms that you may have already heard—APIs, CSS, IP, REST, TCP, URLs, URIs, and XML—as well as some widely used buzzwords: cookies, markup languages, port numbers, and three-tier architectures. More importantly, it demonstrates the importance of design patterns, particularly Model-View-Controller that is at the heart of Rails. Rather than just tell you how to build long lasting software and watch you forget, we believe you must do to understand. It is much easier to try good guidelines if the tools encourage it, and we believe today the best SaaS tools support the Rails framework, which is written in Ruby. Thus, Chapter 3 introduces Ruby. The Ruby introduction is short because it assumes you already know another object-oriented programming language well, in this case Java. As mentioned above, we believe successful software engineers will need to routinely learn new languages and tools over their careers, so learning Ruby and Rails is good practice. Chapter 4 next introduces the basics of Rails and the more advanced features of Rails in Chapter 5 . We split the material into two chapters for readers who want to get started writing an app as soon as they can, which just requires Chapter 4 . While the material in Chapter 5 is more challenging to learn and understand, your application can be DRYer and more concise if you use concepts like partials, validations, lifecycle callbacks, filters, associations, and foreign keys. Readers already familiar with
Image of page 60
Image of page 61

You've reached the end of your free preview.

Want to read all 517 pages?

  • Spring '19
  • Dr.Marcos

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes
A+ icon
Ask Expert Tutors