The document discusses process models and agile methods for web application development. It provides an overview of the Rational Unified Process (RUP) model, including its goals, key aspects, phases, workflows, artifacts, and models. It then discusses agile methods like Scrum and eXtreme Programming (XP), contrasting them with more traditional "heavyweight" models. The document also summarizes various business models for electronic commerce, including business-to-consumer models like portals, e-tailers, content providers, transaction brokers, and market creators.
This document discusses the process of developing a user experience (UX) model for a web application from requirements. It explains that requirements engineering and analysis produce a requirements model and analysis model, which then inform the design of the interaction model or UX model. The UX model defines elements like user interface metaphors, naming conventions, and page layout specifications to guide the development team.
Unit 7 covers web presentation layer patterns including the Model-View-Controller (MVC) pattern and related patterns. It discusses the MVC pattern in detail, dividing an application into three components: the model containing core functionality, the view for displaying information, and the controller for handling user input. It then provides a catalog of MVC-based patterns including page controller, front controller, application controller, and intercepting filter patterns.
The document discusses security principles for web applications, including identifying threats like spoofing and tampering, vulnerabilities, and attacks. It emphasizes authenticating and authorizing users, implementing measures like encryption to ensure confidentiality and integrity of data, and making systems available through techniques such as throttling. The document also provides examples of network, host, and application level threats and corresponding countermeasures.
The document discusses various design patterns and frameworks related to web presentation layers and integrating web and business layers. It covers the Context Object pattern for encapsulating state in a protocol-independent way. It also discusses the Synchronizer Token pattern for controlling duplicate requests and client access flow. For integrating remote web and business layers, it describes the Service Locator and Business Delegate patterns for locating and accessing business services through a centralized lookup mechanism or delegate respectively. Finally, it compares Transaction Script, Domain Model, and Table Module as architectural patterns for the business layer.
This document discusses web-based systems and how they are built. It defines a web-based system as a software system based on World Wide Web Consortium standards that provides web resources like content and services through a web browser. It categorizes different types of web-based systems based on complexity. It also outlines key characteristics of web-based systems, common technologies used to build them like programming languages and frameworks, and considerations for the web engineering process.
The document summarizes various physical architecture patterns for web applications, including single server, separate database, replicated web servers, separate scripting engines, application servers, and J2EE architectures. It also discusses dimensions to consider in architecture design like performance, scalability, and constraints. Additional topics covered include web caching techniques and an overview of cloud computing characteristics and service models.
Testing is the process of evaluating a product to find errors and improve quality. There are different levels of testing including unit testing, integration testing, system testing, and acceptance testing. Usability testing involves having potential users evaluate how easy a website is to use. It is important to test early and often throughout the development process to find and address errors as early as possible.
This document provides an overview of web technologies, including:
- Core technologies like web browsers, web servers, URIs, and HTTP.
- Client-side technologies like HTML, CSS, JavaScript, DOM, AJAX, and HTML5 for enhancing user interfaces.
- Server-side technologies like CGI, PHP, Java servlets, and JSPs for building dynamic web applications.
This document discusses the process of developing a user experience (UX) model for a web application from requirements. It explains that requirements engineering and analysis produce a requirements model and analysis model, which then inform the design of the interaction model or UX model. The UX model defines elements like user interface metaphors, naming conventions, and page layout specifications to guide the development team.
Unit 7 covers web presentation layer patterns including the Model-View-Controller (MVC) pattern and related patterns. It discusses the MVC pattern in detail, dividing an application into three components: the model containing core functionality, the view for displaying information, and the controller for handling user input. It then provides a catalog of MVC-based patterns including page controller, front controller, application controller, and intercepting filter patterns.
The document discusses security principles for web applications, including identifying threats like spoofing and tampering, vulnerabilities, and attacks. It emphasizes authenticating and authorizing users, implementing measures like encryption to ensure confidentiality and integrity of data, and making systems available through techniques such as throttling. The document also provides examples of network, host, and application level threats and corresponding countermeasures.
The document discusses various design patterns and frameworks related to web presentation layers and integrating web and business layers. It covers the Context Object pattern for encapsulating state in a protocol-independent way. It also discusses the Synchronizer Token pattern for controlling duplicate requests and client access flow. For integrating remote web and business layers, it describes the Service Locator and Business Delegate patterns for locating and accessing business services through a centralized lookup mechanism or delegate respectively. Finally, it compares Transaction Script, Domain Model, and Table Module as architectural patterns for the business layer.
This document discusses web-based systems and how they are built. It defines a web-based system as a software system based on World Wide Web Consortium standards that provides web resources like content and services through a web browser. It categorizes different types of web-based systems based on complexity. It also outlines key characteristics of web-based systems, common technologies used to build them like programming languages and frameworks, and considerations for the web engineering process.
The document summarizes various physical architecture patterns for web applications, including single server, separate database, replicated web servers, separate scripting engines, application servers, and J2EE architectures. It also discusses dimensions to consider in architecture design like performance, scalability, and constraints. Additional topics covered include web caching techniques and an overview of cloud computing characteristics and service models.
Testing is the process of evaluating a product to find errors and improve quality. There are different levels of testing including unit testing, integration testing, system testing, and acceptance testing. Usability testing involves having potential users evaluate how easy a website is to use. It is important to test early and often throughout the development process to find and address errors as early as possible.
This document provides an overview of web technologies, including:
- Core technologies like web browsers, web servers, URIs, and HTTP.
- Client-side technologies like HTML, CSS, JavaScript, DOM, AJAX, and HTML5 for enhancing user interfaces.
- Server-side technologies like CGI, PHP, Java servlets, and JSPs for building dynamic web applications.
The document discusses physical architecture layer design, which involves determining how a system will be distributed across computers and the hardware and software that will be used. This includes infrastructure design, hardware specifications, and determining which application software components will run on which hardware. Common application architectures are server-based, client-based, and client-server. The physical architecture design flows from non-functional requirements and specifies the system's hardware and software components.
The document discusses different web frameworks for Java, focusing on Struts 1, Spring MVC, and JavaServer Faces. It provides an overview and examples of how Struts 1 implements the MVC pattern using components like ActionServlet, RequestProcessor, and ActionMappings. It also briefly compares Struts 1 and 2, and outlines key aspects of Spring MVC like flexible request mapping and support for different view technologies.
[DSBW Spring 2009] Unit 07: WebApp Design Patterns & Frameworks (2/3)Carles Farré
This document summarizes various design patterns and frameworks related to web presentation layers and business layers. For web presentation layers, it discusses the Context Object pattern for encapsulating state, the Synchronizer Token pattern for controlling request flow, and different approaches to session state management. It also reviews integration patterns for connecting web presentation and business layers, including the Service Locator and Business Delegate patterns. Finally, it examines common architectural patterns for the business layer such as Transaction Script, Domain Model, and Table Module.
The document discusses various web technologies including:
- Core web technologies like browsers, servers, URIs and HTTP.
- Client-side technologies like HTML, CSS, JavaScript and HTML5.
- Server-side technologies for web applications like CGI, PHP, Java servlets and JSPs.
- How web applications use technologies like application servers to manage business logic and state in a dynamic way.
- Common methods for managing session state including cookies, databases and application servers.
Checking the health of your active directory enviornmentSpiffy
The document discusses checking the health of an Active Directory environment. It covers major components like Active Directory replication, SYSVOL replication, name resolution, and domain controller health. It emphasizes the importance of disaster recovery for Active Directory. Some best practices include regularly monitoring replication, event logs, and domain controller health. It's important to configure backups and have a disaster recovery plan to address issues like data loss or loss of domain controllers.
The document provides an overview of XML and related web technologies including XML, XML Schema, XSL, XQuery, web services using SOAP and WSDL, and RESTful web services. It defines these technologies and provides examples to illustrate their usage and capabilities. The document is intended as a teaching resource to introduce learners to key concepts and standards related to XML, web services, and the semantic web.
Define and Manage Requirements with IBM Rational Requirements ComposerAlan Kan
The document provides an overview of a hands-on lab session on IBM Rational Requirements Composer (RRC). The lab aims to demonstrate how RRC can help teams collaborate to define, manage and trace requirements across the software development lifecycle. The lab covers topics like importing and linking requirements, modeling business processes and use cases, conducting reviews, and generating work items and test cases from requirements. Known issues encountered in the labs are also documented.
The document discusses the Netweaver Development Infrastructure (NWDI) which provides an integrated development environment for application development. It includes a Design Time Repository for source control and versioning, a Component Build Service for compiling and building components, and a Change Management Service for transporting and deploying changes. The NWDI supports distributed development, reusable components, and consistent builds. It provides benefits such as higher development efficiency, controlled source delivery, and centralized change management similar to SAP transports.
The document discusses patterns and best practices for Java EE development. It argues that many criticisms of EJBs are outdated given improvements in EJB 3.1 and Java EE specifications. It presents alternatives like using simple POJOs or introducing lightweight frameworks through interceptors. The document also discusses patterns like entity control boundary, service facade, and introducing services as a finer-grained alternative to session facades.
Jee design patterns- Marek Strejczek - Rule FinancialRule_Financial
The document discusses design patterns for Java EE applications. It covers service facade, session facade, persistent domain object, and fluid logic patterns. Service facade acts as a boundary between the presentation and business layers, encapsulating business logic. Session facade focuses on business logic that is not remotely accessible. Persistent domain object pattern implements business objects that encapsulate both data and behavior. Fluid logic allows executing parts of business logic dynamically using a scripting language.
J2EE is a platform-independent Java-centric environment for developing, building, and deploying web-based enterprise applications. It consists of services, APIs, and protocols that provide functionality for developing multi-tier, web-based applications. J2EE supports component-based development of multi-tier enterprise applications consisting of client, web, EJB, and EIS tiers. Statements are used to send SQL commands and receive data from databases, with PreparedStatements being useful for queries with parameters and CallableStatements for stored procedures.
This document provides an overview of JavaEE and discusses its evolution and key features. It begins with an agenda for the Java World introduction. It then discusses the history and components of Java technology before explaining the different configurations of the Java Platform. The document outlines the evolution of enterprise application development frameworks from single-tier to multi-tier architectures. It introduces JavaEE as an open standard solution and discusses how it provides commonly shared services through a container. The document concludes with a demo of a JavaEE application and overview of improvements in JavaEE 5 including more use of annotations.
The document outlines various roles and responsibilities in the software development process. Project managers plan tasks and track bugs, while business analysts manage requirements. Architects design system architectures and interfaces. Developers write and test code. Database administrators design and maintain databases. Testers create and execute test cases to ensure quality.
Model-Driven Development, the end of the test profession?Johan den Haan
I used this presentation in my keynote talk at the Dutch Testnet 2010 event. For an audience of 500+ professional software testers I explained the basic concepts of Model-Driven Development and gave some food-for-thought about the impact of MDD on the test profession.
Application virtualization is a very hot topic these days. Using this method to provision software to your endpoints allows you to control how the software interacts with your systems. It also allows you to avoid the potential for new applications to disrupt software that is already installed. Attend this session to learn how Novell recommends that you take advantage of these new capabilities—and how you can quickly and easily start to virtualize software releases in your organization.
New CA 2E 8.7 (Synon) and CA 7.1 , Invigorated Mark O'Brien
CA Plex 7.1 introduced new features like .NET ClickOnce deployment and localization support to simplify Windows application modernization. The release focused on improving support for third-party testing tools and adding customer-requested enhancements. CA Plex 7.2 will automate deploying proxies to Layer 7 gateways and enhance SQL support on IBM i systems, with the goal of supporting deployment of Plex business logic as Java web services. Future releases will continue to focus on customer-driven agile development through collaboration programs.
Mike Taulty MIX10 Silverlight 4 Patterns Frameworksukdpe
The document discusses various frameworks and patterns in Silverlight 4, including ASP.NET client application services, WCF data services, WCF RIA services, navigation, search, and extensibility with MEF. It provides an overview and demos of each technology. The presentation encourages attendees to check the schedule for additional in-depth sessions on topics like OData, WCF data services, WCF RIA services, navigation, search engine optimization, and MEF.
The document discusses physical architecture layer design, which involves determining how a system will be distributed across computers and the hardware and software that will be used. This includes infrastructure design, hardware specifications, and determining which application software components will run on which hardware. Common application architectures are server-based, client-based, and client-server. The physical architecture design flows from non-functional requirements and specifies the system's hardware and software components.
The document discusses different web frameworks for Java, focusing on Struts 1, Spring MVC, and JavaServer Faces. It provides an overview and examples of how Struts 1 implements the MVC pattern using components like ActionServlet, RequestProcessor, and ActionMappings. It also briefly compares Struts 1 and 2, and outlines key aspects of Spring MVC like flexible request mapping and support for different view technologies.
[DSBW Spring 2009] Unit 07: WebApp Design Patterns & Frameworks (2/3)Carles Farré
This document summarizes various design patterns and frameworks related to web presentation layers and business layers. For web presentation layers, it discusses the Context Object pattern for encapsulating state, the Synchronizer Token pattern for controlling request flow, and different approaches to session state management. It also reviews integration patterns for connecting web presentation and business layers, including the Service Locator and Business Delegate patterns. Finally, it examines common architectural patterns for the business layer such as Transaction Script, Domain Model, and Table Module.
The document discusses various web technologies including:
- Core web technologies like browsers, servers, URIs and HTTP.
- Client-side technologies like HTML, CSS, JavaScript and HTML5.
- Server-side technologies for web applications like CGI, PHP, Java servlets and JSPs.
- How web applications use technologies like application servers to manage business logic and state in a dynamic way.
- Common methods for managing session state including cookies, databases and application servers.
Checking the health of your active directory enviornmentSpiffy
The document discusses checking the health of an Active Directory environment. It covers major components like Active Directory replication, SYSVOL replication, name resolution, and domain controller health. It emphasizes the importance of disaster recovery for Active Directory. Some best practices include regularly monitoring replication, event logs, and domain controller health. It's important to configure backups and have a disaster recovery plan to address issues like data loss or loss of domain controllers.
The document provides an overview of XML and related web technologies including XML, XML Schema, XSL, XQuery, web services using SOAP and WSDL, and RESTful web services. It defines these technologies and provides examples to illustrate their usage and capabilities. The document is intended as a teaching resource to introduce learners to key concepts and standards related to XML, web services, and the semantic web.
Define and Manage Requirements with IBM Rational Requirements ComposerAlan Kan
The document provides an overview of a hands-on lab session on IBM Rational Requirements Composer (RRC). The lab aims to demonstrate how RRC can help teams collaborate to define, manage and trace requirements across the software development lifecycle. The lab covers topics like importing and linking requirements, modeling business processes and use cases, conducting reviews, and generating work items and test cases from requirements. Known issues encountered in the labs are also documented.
The document discusses the Netweaver Development Infrastructure (NWDI) which provides an integrated development environment for application development. It includes a Design Time Repository for source control and versioning, a Component Build Service for compiling and building components, and a Change Management Service for transporting and deploying changes. The NWDI supports distributed development, reusable components, and consistent builds. It provides benefits such as higher development efficiency, controlled source delivery, and centralized change management similar to SAP transports.
The document discusses patterns and best practices for Java EE development. It argues that many criticisms of EJBs are outdated given improvements in EJB 3.1 and Java EE specifications. It presents alternatives like using simple POJOs or introducing lightweight frameworks through interceptors. The document also discusses patterns like entity control boundary, service facade, and introducing services as a finer-grained alternative to session facades.
Jee design patterns- Marek Strejczek - Rule FinancialRule_Financial
The document discusses design patterns for Java EE applications. It covers service facade, session facade, persistent domain object, and fluid logic patterns. Service facade acts as a boundary between the presentation and business layers, encapsulating business logic. Session facade focuses on business logic that is not remotely accessible. Persistent domain object pattern implements business objects that encapsulate both data and behavior. Fluid logic allows executing parts of business logic dynamically using a scripting language.
J2EE is a platform-independent Java-centric environment for developing, building, and deploying web-based enterprise applications. It consists of services, APIs, and protocols that provide functionality for developing multi-tier, web-based applications. J2EE supports component-based development of multi-tier enterprise applications consisting of client, web, EJB, and EIS tiers. Statements are used to send SQL commands and receive data from databases, with PreparedStatements being useful for queries with parameters and CallableStatements for stored procedures.
This document provides an overview of JavaEE and discusses its evolution and key features. It begins with an agenda for the Java World introduction. It then discusses the history and components of Java technology before explaining the different configurations of the Java Platform. The document outlines the evolution of enterprise application development frameworks from single-tier to multi-tier architectures. It introduces JavaEE as an open standard solution and discusses how it provides commonly shared services through a container. The document concludes with a demo of a JavaEE application and overview of improvements in JavaEE 5 including more use of annotations.
The document outlines various roles and responsibilities in the software development process. Project managers plan tasks and track bugs, while business analysts manage requirements. Architects design system architectures and interfaces. Developers write and test code. Database administrators design and maintain databases. Testers create and execute test cases to ensure quality.
Model-Driven Development, the end of the test profession?Johan den Haan
I used this presentation in my keynote talk at the Dutch Testnet 2010 event. For an audience of 500+ professional software testers I explained the basic concepts of Model-Driven Development and gave some food-for-thought about the impact of MDD on the test profession.
Application virtualization is a very hot topic these days. Using this method to provision software to your endpoints allows you to control how the software interacts with your systems. It also allows you to avoid the potential for new applications to disrupt software that is already installed. Attend this session to learn how Novell recommends that you take advantage of these new capabilities—and how you can quickly and easily start to virtualize software releases in your organization.
New CA 2E 8.7 (Synon) and CA 7.1 , Invigorated Mark O'Brien
CA Plex 7.1 introduced new features like .NET ClickOnce deployment and localization support to simplify Windows application modernization. The release focused on improving support for third-party testing tools and adding customer-requested enhancements. CA Plex 7.2 will automate deploying proxies to Layer 7 gateways and enhance SQL support on IBM i systems, with the goal of supporting deployment of Plex business logic as Java web services. Future releases will continue to focus on customer-driven agile development through collaboration programs.
Mike Taulty MIX10 Silverlight 4 Patterns Frameworksukdpe
The document discusses various frameworks and patterns in Silverlight 4, including ASP.NET client application services, WCF data services, WCF RIA services, navigation, search, and extensibility with MEF. It provides an overview and demos of each technology. The presentation encourages attendees to check the schedule for additional in-depth sessions on topics like OData, WCF data services, WCF RIA services, navigation, search engine optimization, and MEF.
This document promotes student-centered learning approaches like Genius Hour and ePortfolios, where students spend time on self-directed creative projects and reflect on their learning process. It references advocates of creativity in education like Sir Ken Robinson and provides hashtags and Twitter handles to connect educators interested in these topics. The document encourages sharing ideas to support student creativity and connected learning.
Flipping the ela classroom cawp versionMrsHardin78
This document discusses flipping the classroom model for an English/Language Arts class. It begins by addressing common myths about flipping, noting that videos do not need to be lectures created by the teacher, can take various forms, and that flipping does not always require extra time or only work for quantifiable topics. Next, it provides examples of how grammar, vocabulary and literary symbolism could be taught using a flipped model with video instruction, guided notes, activities and assessments both in-class and as homework. Lastly, it offers tips on creating reliable video content and accessing free or low-cost options for recording and hosting videos.
98-7 FM radio is celebrating 5 years on the air. The station is thanking listeners for their support over the past 5 years. 98-7 asks what else they can do for their listeners going forward.
La Unión Europea ha propuesto un nuevo paquete de sanciones contra Rusia que incluye un embargo al petróleo ruso. El embargo se aplicaría gradualmente durante seis meses para el petróleo crudo y ocho meses para los productos refinados. El objetivo es aumentar la presión sobre Rusia para que ponga fin a su invasión de Ucrania.
This short poem describes a wedding ceremony taking place in Salzburg, Austria between partners from the UK and Austria. The couple completes a star-matching task, signifying an auspicious start to building a home together where they can find joy.
Stephanie Neri presented on social media tools for educators. She found Twitter, LinkedIn, and Delicious to be the most useful for accessing research, making professional connections, and organizing information. Through using these tools, she learned about new autism research and how to market her skills to employers. Some challenges were navigating the sites and understanding technical language. Neri also discussed how her Moodle course provided online learning resources, teaching strategies, and a way to easily contact her teacher at her own pace through videos and instructions. She decided to take another Moodle class to continue utilizing online tools and feeling more confident accessing online information to improve her teaching.
Twitter and Blogging by @gallit_z and @hughtheteacherGallit Zvi
This document discusses using Twitter and blogging in the intermediate classroom. It introduces the concepts of Web 2.0 technologies, participation, collaboration, and using the internet in new ways. Specific reasons given for using Twitter include making connections through personal learning networks, collaboration, and finding new resources. Reasons to blog with students include giving them an authentic audience, increasing engagement and motivation, improving writing and reading skills, and allowing students to take ownership of their learning.
This document discusses Genius Hour, which allows students one hour per week to pursue their own interests and questions. It emphasizes giving students autonomy to follow their passions. Genius Hour promotes creativity, innovation, collaboration and critical thinking. The document provides examples of how Genius Hour has been implemented, including one day per week or month devoted to the program. Resources are also listed for those wanting more information on setting up Genius Hour.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
This document discusses content related to color and weather. It mentions color without providing details on specific colors. It also briefly references weather but does not specify weather patterns or conditions. The document does not provide enough contextual information to create a more descriptive summary.
21st century learning focuses on applying knowledge to new situations, analyzing information, collaborating, solving problems, and making decisions using educational technologies. It involves activities like Genius Hour where students pursue their passions, and creating ePortfolios for self-reflection. Students also collaborate globally through blogging and Twitter to make connections beyond the classroom.
Este documento presenta criterios de diseño y construcción de tomas tirolesas para la captación de agua en ríos de montaña. Describe 7 obras implementadas en Cochabamba, reportando su contexto, características constructivas y dificultades de funcionamiento. También analiza la relación entre el diseño técnico de las tomas y la gestión del agua por parte de los usuarios, identificando problemas de operación y mantenimiento originados tanto en deficiencias de diseño como en la construcción e intervención en la cuenca. El documento provee recomend
This document provides a room-by-room summary of a playschool called "Sanjivni". It describes the various facilities available such as the dance room, reception area, activity room, sleeping room, kitchen, restrooms, and principal's office. It also provides a critical analysis of several rooms that need improvements in storage, organization, cleanliness, and maintenance.
This document discusses several kitchen tools used in baking and food preparation:
- A spatula is a small, flat implement used to mix, spread, and lift foods, as well as other materials like paint or plaster. It derives its name from a Latin word meaning flat piece of wood.
- A pastry blender is used to cut solid fat like butter or shortening into flour to make pastries. It has narrow metal strips or wires attached to a handle.
- A rolling pin is used to shape and flatten dough, and comes in roller or rod styles made of various materials.
[DSBW Spring 2009] Unit 03: WebEng Process ModelsCarles Farré
The document discusses various process models and business models for web application development and electronic commerce. It provides an overview of the Rational Unified Process (RUP) as a process model, describing its key aspects, phases, artifacts, and workflows. It also discusses agile methods and eXtreme Programming (XP) as alternative process models. For business models, it describes categories such as business-to-consumer, business-to-business, and emerging models like consumer-to-consumer and mobile commerce.
The document discusses several software development process models including waterfall, iterative development, prototyping, RAD, spiral, RUP, and agile processes. The waterfall model is a linear sequential process while iterative development allows for incremental improvements. Prototyping allows users to provide early feedback. RAD combines waterfall and prototyping and emphasizes rapid development. Spiral model iterates through risk analysis, development, and planning phases. RUP is object-oriented and divided into cycles. Agile processes emphasize working software, incremental delivery, flexibility, and customer involvement.
The document outlines an iterative methodology for deploying Aras Innovator. It discusses dividing projects into manageable phases like inception, elaboration, construction, and transition. Each phase has objectives and milestones. The methodology emphasizes iterative design, managing requirements, continuous verification, and controlling changes. It provides tips for implementation like using visual prototypes, breaking work into components, and ensuring quality through user testing.
This document provides information on the Software Engineering course with code 210253. It is a 3 credit course with a mid-semester exam worth 30 marks and an end-semester exam worth 70 marks. The syllabus covers topics like introduction to software engineering, software process models, prescriptive process models (waterfall, incremental, evolutionary), and agile software development. It also discusses concepts like software engineering fundamentals, process frameworks, generic process activities, prescriptive process models, evolutionary models, concurrent development model, and principles of software engineering practice.
Ravindra Prasad has over 10 years of experience as a Software Development Engineer and SDET. He has extensive experience developing automation frameworks using C# and technologies like Selenium, Coded UI, and Visual Studio. Some of his responsibilities include writing test automation scripts; developing keyword-driven and page object frameworks; and managing teams of 4-7 people on projects for clients such as Dell and Microsoft. He is proficient in languages like C# and databases like SQL Server, and has experience across the full development lifecycle from requirements to delivery.
Collaborate 2012 - the never ending road of project management presentation c...Chain Sys Corporation
The document discusses a presentation on project management best practices for Oracle R12 implementations. It provides an overview of the presenting organization, CHAIN SYS, and covers topics like technology and project management trends, R12 development issues, agile development methodology, project management disciplines, and lessons learned. CHAIN SYS recommends a hybrid implementation methodology combining features of Oracle's methodologies to manage R12 projects.
This document contains a summary of Nilesh A. Chitale's experience and qualifications. He has over 12 years of experience in software development and management. Some of his roles include architect, tech lead, and senior developer. He has worked on projects for banking and financial clients. His technical skills include C#, ASP.Net, SQL Server, and Agile methodologies. His experience includes several architect roles where he performed tasks like design reviews, code reviews, and requirements gathering.
This document discusses Boehm's top 10 principles of conventional software management and important trends in improving software economics. It also covers the three generations of software development (conventional, transition, and modern practices), comparing their characteristics. Finally, it lists and explains 10 principles of conventional software engineering and the top 10 principles of modern software management.
Case Study: Practical tools and strategies for tackling legacy practices and ...Alejandro S.
In this talk you will learn how strategic tools like Wardley Maps, the C4 model and DDD’s strategic design helped a struggling CTO to fight against a crumbling monolith and the organizational practices that allowed its creation.
Among other things we will cover:
* How to plan, communicate and challenge strategies.
* Why strategy and thinking strategically is important for software developers.
* High-level overview of Simon Brown’s C4 Model
* High-level overview of DDD’s strategic design
* DDD Context Mapping
* High-level overview Wardley Maps.
* Wardley Maps: Landscape.
* FUN random facts about software development in startups :)
This document provides an introduction to the Eclipse Process Framework Composer tool. It discusses how the tool can be used to manage libraries of reusable method content and assemble customized processes for projects. The tool addresses the needs of aligning flexible development processes with business processes and supporting modern agile development practices. It separates reusable method content from its application in processes to provide a knowledge base and process engineering capabilities.
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, incremental, spiral, rapid application development (RAD), dynamic systems development method (DSDM), adaptive software development, and agile methods. It provides an overview of the key characteristics, strengths, weaknesses, and types of projects that each model is best suited for. Tailored SDLC models are recommended to customize processes based on specific project needs and risks.
The document discusses systems analysis and design. It provides an overview of the software development life cycle (SDLC) and various methodologies including Rational Unified Process (RUP), Agile, Scrum, eXtreme Programming (XP), and others. It describes the phases of RUP including inception, elaboration, construction, and transition. It also discusses key aspects of RUP like risk-driven development, use case driven development, and architecture-centric design.
Software Factories in the Real World: How an IBM WebSphere Integration Factor...ghodgkinson
This document discusses how an automotive retailer set up an efficient software factory using IBM tools like Rational Software Architect and WebSphere Message Broker to integrate a new point of sale system with their SAP backend. The software factory employed techniques like model-driven development and continuous integration to help scale development and keep customers satisfied. Key practices that helped succeed included tighter architectural control using Rational Software Architect models and service definitions, and keeping the distributed team coordinated using Rational Team Concert for planning, source control, and tracking progress across locations. The integrated approach and tools helped the retailer successfully complete the large integration project.
This slide deck Introduces Chef and its role in DevOps. The agenda of the deck is as follows:
- A Review of DevOps
- BMs Continuous Delivery solution
- Introduction to Chef
- Chef and Continuous Delivery
Read more on DevOps: http://sdarchitect.wordpress.com/understanding-devops/
- The document is a resume for Nilesh R. Surange, who has over 9.5 years of experience as an IT professional developing enterprise applications using technologies like Java, Eclipse IDE, and Agile methodologies.
- He has worked on projects for clients such as Discover Financial Services, Capgemini Financial Services, and Avibha IT Solutions, developing applications using Java, J2EE, Struts, Spring, Hibernate and relational databases.
- His most recent role was as a senior consultant for Capgemini America where he worked on the DBV2 platform for Discover Financial Services, contributing to modules, requirements gathering, testing, and serving as the primary contact.
Experienced Software Engineer with a demonstrated history of working in the information technology and services industry. Skilled in ETL , Business Intelligence (BI), Oracle Data Integrator (ODI) , OBIEE , SQL , PLSQL and JAVA. Strong engineering professional with a Bachelor of Engineering (B.E.) focused in Information Technology from B.V.B.C.E.T..
The document provides information on various software versions used for engineering drawings, documents, technical illustrations, web browsing and document viewing. It lists applications such as AutoCAD, CorelDRAW, Microsoft Office, Netscape Navigator and Acrobat software. It also provides a link for an up-to-date list of software versions.
Subhadra Banerjee has over 10 years of experience in software development using technologies like Java, J2EE, Documentum, and Oracle. He has worked as a senior systems engineer, lead engineer, and project lead on various projects for clients in banking, energy, and other industries. His experience includes requirements gathering, design, development, testing, deployment, and support of Documentum and Java applications.
We had this presentation running on one of the screens in our booth at the April 4, 2013, Innotech Dallas/SharePoint TechFest. We have been excited by the developments in the latest release of Visual Studio and it's ability to work seamlessly with Microsoft's Azure.
Similar to Unit03: Process and Business Models (20)
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Climate Impact of Software Testing at Nordic Testing Days
Unit03: Process and Business Models
1. Unit 3
Process Models for Web Application Development
RUP
Agile methods
Business Models for Electronic Commerce
dsbw 2011/2012 q1 1
2. Process Models
A web/software development process model has four roles:
Provide guidance about the order of a team's activities.
Specify artifacts that should be developed.
Direct the tasks of individual developers and the team as a whole.
Offer criteria for monitoring and measuring the project's products
and activities.
The process model should define the workflows, activities, artifacts, and
roles in the development process
A workflow is set of activities—requirements, analysis, design,
implementation, testing, and deployment—that ultimately produce
tangible and observable results: artifacts
An artifact is any persistent piece of information that is produced during
the process: models, source code, documents, etc.
Artifacts often undergo significant change during the process, resulting in
series of versions that should be controlled and traceable.
dsbw 2011/2012 q1 2
3. The Rational Unified Process (RUP)
Goal: to support the development of a high-quality product
within a fixed period of time and at a fixed price.
Use case driven
Key aspects: Architecture-centric
Iterative and incremental
dsbw 2011/2012 q1 3
4. RUP: Overview
Analyze
business and
perceived
problems
Analyze
Develop Develop
the Deploy
vision project Iterate
understood system
document plan
problem
[Pass acceptance critera]
Develop
domain
model Maintain
<<defines>> system
Manage artifact versions
dsbw 2011/2012 q1 4
5. RUP: Iterate
UP Phases
Incept ion Elaborat ion Const ruct ion Transit ion Product ion
Workflows
Requirements
Analy sis
Design
Implementation
Test
Support
Iterations #1 #2 #n-1 #n
dsbw 2011/2012 q1 5
6. RUP Models: Dependencies and traceabilities
Project
Management
Model
Requirements
Engineering
Model Test
Model
Domain
Model
Analysis Design Implementation
Model Model Model
Deployment
Model
dsbw 2011/2012 q1 6
7. Artifacts in the Requirements Engineering Model
Vision Document (revised)
Functional requirements
Non-functional requirements:
Business requirements: standards, legislations, regulations
Architectural requirements: acceptable response times,
acceptable Web browser versions, etc.
New! User experience (UX) document:
Defines the targeted look-and-feel for the application, the
emotion that the application is trying to establish with the user
The user experience (UX) team is responsible for both
developing and implementing this document .
dsbw 2011/2012 q1 7
8. Artifacts in the Analysis Model
Use Case Model
Use Case diagrams
Conceptual Model
Domain class diagrams
Textual integrity constraints
System Behavior Model
System’s sequence diagrams
System’s operation contracts
State Model
State diagrams
dsbw 2011/2012 q1 8
9. Artifacts in the Design Model
Physical Architecture
Description of architectural tiers, processes, protocols, etc.
Logical Architecture:
Web Presentation Layer:
External Design (UX Model)
Internal Design
Class Diagrams using the Web Application Extension for
UML
Sequence Diagrams
Domain Layer
Data Access Layer
Database Design
dsbw 2011/2012 q1 9
10. The Process Model should be tailored considering …
The development team:
Large vs. small teams
Heterogeneous vs homogeneous teams
Skill level
The nature of the application
Human-critical applications: medical devices, spacecraft systems,
thermonuclear controls, etc.
Web applications: they are not human-critical. Still, other factors
should be considered:
Evolving technologies
Greater emphasis on nonfunctional requirements: security, availability,
accessibility, etc.
Priorities:
Fast vs. complete
Fast vs. correct
dsbw 2011/2012 q1 10
11. Another way of building software is possible …
Most process models are too “heavy”
Too many things are done with no direct relation with
programming software.
Traditional process models are too rigid
The do not fit well when requirements are incomplete and
unstable.
They are not appropriate when frequent releases and short
development iterations are required.
Customers should participate more actively
Lesser focus on the process and more on people
Alternative: Agile methods
dsbw 2011/2012 q1 11
12. Agile Methods
Examples:
Agile Modeling
Agile Unified Process (AUP)
Agile Data Method
DSDM
Essential Unified Process (EssUP)
Extreme Programming (XP)
Feature Driven Development (FDD)
Open Unified Process (OpenUP)
Scrum
Lean software development
All of them are adhered to the Agile Alliance
(www.agilealliance.org) and its Manifesto
dsbw 2011/2012 q1 12
13. Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working Software over comprehensive documentation
Customer Collaboration over contract negotiation
Responding to Change over following a plan
That is, while there is value in the items on the right,
we value the items on the left more.
dsbw 2011/2012 q1 13
14. The Twelve Principles of Agile Development
1) Customer satisfaction through early and continuous delivery of
valuable software
2) Welcome changing requirements, even late in development
3) Deliver working software frequently (2 weeks – 2 months)
4) Business people and developers must work together daily
5) Build projects around motivated individuals
6) Face-to-face conversation
7) Working software is the primary measure of progress
8) Agile processes promote sustainable development
9) Continuous attention to technical excellence and good design
10) Simplicity
11) Self-organizing teams.
12) Regular adaptation to changing circumstances
dsbw 2011/2012 q1 14
15. eXtreme Programming (XP)
The four variables to be controlled
Cost, Time, Quality, and Scope
The five values to be promoted:
Communication, Simplicity, Feedback, Courage and Respect
The five principles that should guide us:
Rapid feedback, Assuming simplicity, Incremental changes,
Embracing change, Quality work
The twelve practices:
Planning game, small releases, simple designs, automated
testing, continuous integration, refactoring, pair programming,
collective ownership, 40-hour week, on-site customer, coding
standard, metaphor
dsbw 2011/2012 q1 15
16. The XP Process
[changed/new requirement] [next iteration]
[project end]
Release Iteration Publication
Planning [all acceptance
tests successful]
[otherwise]
dsbw 2011/2012 q1 16
19. Scrum Roles
Pigs
Product Owner: The person responsible for maintaining the
Product Backlog by representing the interests of the
stakeholders.
Scrum Master: The person responsible for the Scrum process,
making sure it is used correctly and maximizes its benefits.
Scrum Team: A cross-functional group of people (5 – 9)
responsible for managing itself to develop the product.
Chickens
Stakeholders (customers, vendors): They are only directly
involved in the process during the sprint reviews.
Managers: People who will set up the environment for the
product development organizations.
dsbw 2011/2012 q1 19
20. Scrum Artifacts
Product Backlog
A list of product requirements – functional and non-functional -
prioritized by organizational value
Each Product Backlog will decompose into several Sprint
Backlogs
Sprint Backlog
A prioritized list of tasks to be completed during the sprint.
Tasks should last between 4 and 16 hours of work
Sprint Burnout chart
publicly displayed chart
showing remaining work in
the sprint backlog
Updated every day
dsbw 2011/2012 q1 20
21. Scrum Ceremonies
Spring Planning Meeting
At the beginning of the sprint cycle, the Team selects items
from the product backlog they can commit to completing
Sprint backlog is generated
Daily Scrum
15 minutes, stand up, at the same location and same time
All are welcome, but only pigs speak to answer the three
questions:
What have you done since yesterday?
What are you planning to do today?
Is anything in your way?
Helps avoid other unnecessary meetings
dsbw 2011/2012 q1 21
22. Scrum Ceremonies (cont.)
At the end of a sprint cycle, two meetings are held: The Sprint
Review Meeting and The Sprint Retrospective
Sprint Review Meeting (The Demo)
Team presents to management, customers, users and the Product
Owner the product increment that has been built during the Sprint
All product backlog items selected for Sprint are included in the demo
Afterward, product backlog might be re-arranged, or decision made
to release early (or fail fast)
Sprint Retrospective:
Team, Scrum Master, and (optionally) Product Owner reflect on the
past sprint:
What went well?
What can be improved?
dsbw 2011/2012 q1 22
23. Agile vs. Heavyweight: A comparison
Agile Methods Heavyweight Methods
Approach Adaptive Predictive
Success Business Value Conformation to plan
Measurement
Project Size Small Large
Management Style Decentralized Autocratic
Perspective to Change Change Adaptability Change Sustainability
Culture Leadership-Collaboration Command-Control
Documentation Low Heavy
Emphasis People-Oriented Process-Oriented
Cycles Numerous Limited
Domain Unpredictable/Exploratory Predictable
Team Size Small/Creative Large
Upfront Planning Minimal Comprehensive
Return on Investment Early in the project End of the project
dsbw 2011/2012 q1 23
24. Agile vs. Heavyweight: When they should be used
Agile Methods Heavyweight Methods
Objective Rapid Value High Assurance
Scope (requirements) Subject to change Well Known
Largely emergent Largely Stable
Unknown, Uncertain
Resources (money, Uncertain budget Sufficient Budget
infrastructure) Money tight
Time Unclear & Not well Defined Clear & Defined Milestones
Milestones
Risks Unknown risks Well understood risks
Major Impact New Minor Impact
Technology
Architecture Design for current needs Design for current and future
needs
Developers Agile, co-located, Process-oriented, Adequately
collaborative Skillful
Customers Collaborative, dedicated, Knowledgeable, representative,
co-located, knowledgeable collaborative
Refactoring/Cost of Inexpensive Expensive
Change
dsbw 2011/2012 q1 24
26. The Business Process Engineering Hierarchy
Information strategy planning (ISP)
strategic goals defined
success factors/business rules identified
business model created
Business area analysis (BAA)
processes/services modeled
interrelationships of processes and data
(Web) Application Engineering
modeling applications/procedures that
address (BAA) and constraints of ISP
dsbw 2011/2012 q1 26
27. Business Models
Business Model
A set of planned activities (sometimes referred to as business
processes) designed to result in a profit in a marketplace.
E-commerce Business Model
A business model focused to use the characteristics and
opportunities of Internet and the Web in a strategic way
dsbw 2011/2012 q1 27
28. E-commerce Business Model Categories
Business-to-Consumer (B2C)
Business-to-Business (B2B)
Consumer-to-Consumer (C2C)
Peer-to-Peer (P2P)
Mobile commerce (M-commerce)
dsbw 2011/2012 q1 28
29. B2C Models (1/3)
Portal
Offers an integrated package of services and content such as search,
news, e-mail, chat, downloads, etc.
Variants:
Horizontal/General: Yahoo.com, MSN.com
Vertical/Specialized (Vortal): Universia.es
Revenue model: Advertising, subscription fees, transaction fees.
E-tailer (Electronic retailer)
Online version of retail store.
Variants:
Virtual merchant: Amazon.com
Click-and-mortar: capraboacasa.com
Online mall: fashionmall.com
Manufacturer-direct: dell.com
Revenue model: Sales of goods, transaction fees.
dsbw 2011/2012 q1 29
30. B2C Models (2/3)
Content Provider
Information and entertainment providers such as newspapers, sports
sites, etc.
Revenue model: Advertising, subscription fees, affiliate referral fees.
Transaction broker
Processors of online sales transactions, such as stockbrokers and
travel agents.
Revenue model: transaction fees
Market creator
Creators of virtual markets that bring buyers and sellers together.
Variant: online auctions (eBay.com)
Revenue model: transaction fees
dsbw 2011/2012 q1 30
31. B2C Models (3/3)
Service provider:
Companies that make money by selling a service, rather than a
product.
Revenue model: sales of services.
Community Provider
Sites where individuals with particular interests, hobbies and
common experiences can come together and compare notes.
Revenue model: Advertising, subscription, affiliate referral fees.
dsbw 2011/2012 q1 31
32. B2B Models
B2B Hub: Brings buyers and sellers together to reduce
procurement costs.
E-Distributor: Connecting businesses directly with other
businesses, reducing sales cycles and mark-up.
B2B Service Provider
Traditional: Supports companies through online business services.
Application Service Provider (ASP): Rents Internet-based software
applications to businesses.
Matchmaker: Helps businesses find what they want and need on
the Web
Infomediary
Audience Broker: Gathers information about consumers and uses it to
help advertisers find the most appropriate audience
Lead Generator: Gathers customer data, and uses it to direct vendors
to customers.
dsbw 2011/2012 q1 32
33. Emergent Business Models
Consumer-to-Consumer (C2C)
Electronically-facilitated transactions between consumers
through some third party
Existent model: Market Creator (B2C)
Peer-to-Peer (P2P)
Use of P2P networks for business: besides File Sharing,
companies are also interested in Distributing Computing,
Content Distribution, e-market place, Distributed Search
engines, Groupware and Office Automation via P2P network.
M-commerce
A new distribution channel: mobile devices
dsbw 2011/2012 q1 33
34. References
CONALLEN, J. Building Web Applications with UML Second
Edition. Addison-Wesley 2002.
KAPPEL, Gerti et al: Web Engineering. Wiley, 2006. Chapter
10
KHAN, Ali. A Tale of two Methodologies: Heavyweight versus
Agile. Minor Research Project in IS 615-690, University of
Melbourne, 2004.
R. G. Pressman, D. Lowe: Web Engineering. A Practitioner’s
Approach. McGraw Hill, 2008. Chapters 2-3.
Agile Software Process Models:
http://www.rspa.com/spi/process-agile.html
dsbw 2011/2012 q1 34