Designed in collaboration with Infosys Limited

Transcription

1 Proposal for Introduction of New Industry Course in Engineering Curriculum Agile Software Development - Deliver Software Better Everyday Designed in collaboration with Infosys Limited Version

2 Contents 1. Background Overview of the Course Design Learning outcomes Course Schedule Summary Course contents Tutorials Practical Exposure Infrastructure Requirements Hardware and Software Requirements Software required for Tutorials and Practical: Mode of Examination Faculty Enablement Courseware & Reference Books: Actions: Contact Details: Conclusion:... 7 Page: 2

3 1. Background Our college has partnered with Infosys Limited to roll-out Campus Connect Program. Under this program we have been conducting trainings leveraging IT Industry-Ready program for CS students. Our faculty was enabled in delivering these courses. Infosys is willing to extend the relationship with our college by collaboratively designing a new industry course Agile Software Development. The purpose of this proposal is to describe the contents of the new course, its benefits and seek approval to start the course offering effective Jan Overview of the Course Design 2.1 Synopsis: The proposed course exposes the CS/IT/B.Sc (IT)/M.Sc.(IT)/MBA(IT/IS) students to Agile Software Development. The core modules of this course include agile fundamentals, scrum framework, agile testing, agile software design & programming and industry trends. This course is independent of any organization / product / technology. 2.2 Prerequisites: Awareness of basics of software engineering concepts and waterfall methodology Exposure to any object oriented programming language such as Java, C#. 2.3 Assumptions: 1. This course will be applicable to B.Tech. CS/IT/MCA 2. The duration of the course will be one semester 3. The course design follows university curriculum standards 4. There will be a compulsory final examination 5. The college will leverage existing Lab & IT infrastructure 3. Learning outcomes At the end of this elective, student will be able to: 1. Understand the background and driving forces for taking an Agile approach to software development 2. Understand the business value of adopting Agile approaches 3. Understand the Agile development practices 4. Drive development with unit tests using Test Driven Development 5. Apply design principles and refactoring to achieve Agility 6. Deploy automated build tools, version control and continuous integration 7. Perform testing activities within an Agile project Page: 3

4 4. Course Schedule Summary Here it is illustrated for one semester course: Duration of the Course Number of Weeks Total Lecture hours Total Tutorial hours Total Practical Hours Total Credit One Semester Weeks 3 hours per week 2 hours per month 2.5 hours per week 3 * Total lecture hours includes classroom hours and demonstration of concepts using appropriate agile tools 5. Course contents 5.1 Unit I: Fundamentals of Agile: 9 hours The Genesis of Agile, Introduction and background, Agile Manifesto and Principles, Overview of Scrum, Extreme Programming, Feature Driven development, Lean Software Development, Agile project management, Design and development practices in Agile projects, Test Driven Development, Continuous Integration, Refactoring, Pair Programming, Simple Design, User Stories, Agile Testing, Agile Tools 5.2 Unit II: Agile Scrum Framework: 9 hours Introduction to Scrum, Project phases, Agile Estimation, Planning game, Product backlog, Sprint backlog, Iteration planning, User story definition, Characteristics and content of user stories, Acceptance tests and Verifying stories, Project velocity, Burn down chart, Sprint planning and retrospective, Daily scrum, Scrum roles Product Owner, Scrum Master, Scrum Team, Scrum case study, Tools for Agile project management 5.3 Unit III: Agile Testing: 8 hours The Agile lifecycle and its impact on testing, Test-Driven Development (TDD), xunit framework and tools for TDD, Testing user stories - acceptance tests and scenarios, Planning and managing testing cycle, Exploratory testing, Risk based testing, Regression tests, Test Automation, Tools to support the Agile tester 5.4 Unit IV: Agile Software Design and Development: 10 hours Agile design practices, Role of design Principles including Single Responsibility Principle, Open Closed Principle, Liskov Substitution Principle, Interface Segregation Principles, Dependency Inversion Principle in Agile Design, Need and significance of Refactoring, Refactoring Techniques, Continuous Integration, Automated build tools, Version control 5.5 Unit V: Industry Trends: 9 hours Market scenario and adoption of Agile, Agile ALM, Roles in an Agile project, Agile applicability, Agile in Distributed teams, Business benefits, Challenges in Agile, Risks and Mitigation, Agile projects on Cloud, Balancing Agility with Discipline, Agile rapid development technologies Page: 4

5 6. Tutorials The purpose of 2 hour tutorial per month is to help the students to explore points outside the prescribed material and to enhance their learning. The assignments for course could include the following. Seminars from the topics related to Agile Software Development such as Agile on Cloud, Agile Design Principles, Agile ALM, Test Driven Development etc. Relevant lab exercises to get exposure to various tools such as following to execute Agile projects. These are example open source tools and students can use any other tool for respective area/scope of work: S.No. Tool Name Usage Area / Scope 1 AgileFant Project Life Cycle Management 2 SVN Version Control 3 Jenkins Continuous Integration 4 JUnit Test Driven Development 5 ANT Build Tool 6 QAliber / Cucumber Test Automation 7. Practical Exposure Students should implement (and learn to use the tools to accomplish this task) the following during Practical hours: (illustrative only) 1. Understand a given business scenario and identify product backlog, user stories and sprint tasks 2. Define user stories for a given feature 3. Fill user stories, sprint schedule and sprint tasks in an Agile tool such as AgileFant 4. Write unit tests aligned to xunit framework for TDD 5. Refactor a given design for next sprint requirements 6. Execute continuous integration using a tool such as Jenkins 8. Infrastructure Requirements 8.1 Hardware and Software Requirements Pentium P4, 2.8 GHz or higher 512MB (or higher) RAM, 40 GB (or higher) HD Windows XP with SP2 (or higher) MSOffice 2003, IE 6.0, IIS 6.0, Anti-Virus Software 8.2 Software required for Tutorials and Practical: Eclipse/NetBeans IDE, SVN, AgileFant, Jenkins, JUnit, ANT, QAlibe/Cucumber Page: 5

6 9. Mode of Examination The final examination carries 50 Marks. The Institute will conduct all the assessments. Internal assessments carry 50 Marks which includes Theory Assessment (30 Marks), Practical / Project Work (20 marks) Theory Assessments to be conducted based on CAMP methodology 10. Faculty Enablement The Faculty will be enabled by Infosys on the course contents, Industry practices, tools usage and case studies etc. for duration of one week before the commencement of course. 11. Courseware & Reference Books: The courseware including PowerPoint and notes are available for the Elective. In addition, following reference books can also be used: Agile Software Development with Scrum By Ken Schawber, Mike Beedle Publisher: Pearson Agile Testing: A Practical Guide for Testers and Agile Teams By Lisa Crispin, Janet Gregory Publisher: Addison Wesley Agile Software Development, Principles, Patterns and Practices By Robert C. Martin Publisher: Prentice Hall Agile Software Development: The Cooperative Game By Alistair Cockburn Publisher: Addison Wesley User Stories Applied: For Agile Software By Mike Cohn Publisher: Addison Wesley 12. Actions: 1. The college needs to send the Board of Studies Approval letter on college letter head to Infosys. 2. Identify one department to own the responsibility of course content, assignments, projects, software tools etc. (Preferable CS/IS Department) 3. Identify faculty from CS/IS/MCA department for rollout and faculty training 4. Identify and allocate resources like classrooms, labs, necessary hardware and software for rollout. 5. Complete readiness check before the rollout Page: 6

7 13. Contact Details: The Infosys point of contact can be reached for more info. In addition, the Institute SPoC can also be reached for additional info Department owning the responsibility of Course Content: The HOD S / Faculty Names and their Id, owning the course content of Elective are to be mentioned. S. No. Name Phone Number Faculties handling the Elective rollout: The faculty names and their Id, handling the Elective rollout are to be mentioned. S. No. Name / Dept Phone Number Conclusion: Introduction of the collaboratively designed elective will significantly help the engineering/management students to get an exposure to Agile Software Development domain and understand the applicability of concepts using open source tools and leverage the knowledge gained as a competitive edge in their career in software development. Hence, requesting for approval for adopting these electives in your curriculum. Page: 7