Software Engineering - IT Library : ZDNet Asia

Case Studies

Vendor Webcast

Show all content

Title Date Added Company

Optimizing Agile for Your Organization 2008-09-02 Construx Software Builders

Many organizations are interested in becoming Agile but wonder where to start. They want to ensure that their Agile adoption will achieve the desired benefits, goals, and objectives. This white paper outlines the major organization, cultural, and project considerations that are critical to a successful Agile adoption. It provides a starting point that works for most projects and organizations.

Tags: Software Project Management, Methodology, Services, Application Development

Momentum Webcast: Can Process Improvement and Application Lifecycle Management Really Improve Your Business? (Level 100) 2008-06-25 Microsoft

The term Application Lifecycle Management (ALM) is attracting significant attention from tool vendors, research groups, and industry thought leaders. Although proactively managing the application throughout the life cycle seems to be a simple concept, in fact there are seemingly innumerable ways to accomplish the goals of ALM. Coordinated toolsets, the Capability Maturity Model, innovative modeling techniques, and commercially available processes all provide pieces of this frequently misunderstood and often complex puzzle. This webcast discusses the basic tenets of Application Lifecycle Management, describe what kinds of projects benefit most from ALM, explain how the Microsoft Visual Studio Team System supports this initiative, and examine why a repeatable, pragmatic software development process cannot be overlooked when implementing ALM.

Tags: Application Development

The Software Development Life Cycle for Web 2.0: Realize the Benefits of Agile Development 2008-05-27 IBM

Any software development life cycle must be properly organized before the developer can expect to successfully execute a project. This is also true of Web 2.0, where a well-planned life cycle will let the developer realize the vision of building Web services in shorter development cycles, allow quick testing and deployment, and provide for service versioning. In this paper, get to know the software development life cycle for Web 2.0-based applications. Web 2.0 application-development processes need to be more agile than standard development methodologies allow for. In a Web 2.0 world, the users are going to be more agile in their thinking, will want things more quickly, and are getting used to rapid change. The role of Web 2.0-enabled content-management tools is becoming clear.

Tags: Web Services, Application Development

Adopting Agile Development, Part 3: The Role of Agile Stakeholders 2008-05-20 IBM

Part 1 of this series introduced agile processes, the benefits of using them, and the requirements placed on the organization that uses them. Part 2 discusses how different types of organizations, such as start-ups, product companies, and small and large organizations, adapt to agile development. This paper discusses the different types of stakeholders in an agile process and what their roles entail. Stakeholders in the Srum process are highlighted. In software development, a stakeholder is a party who affects, or can be affected by, an organization's actions. The stakeholders are the entities within or outside of an organization that sponsor a project, have an interest in it, or stand to gain from the results of the project.

Tags: Application Development

Documenting Software Architecture, Part 2: Develop the System Context 2008-05-13 IBM

Part 1 of this series explained the importance of a disciplined approach to documenting software architecture. It also introduced commonly used mechanisms to capture the architectural artifacts used in a typical software development process. This paper continues the discussion and focuses on the first important architecture artifact: the system context. Learn how to document the system context information with diagrams and information flows.

Tags: Application Development

Requirements Modeling, Part 2: Build Your New Design 2008-04-29 IBM

After the developer has designed a new architecture, he is eager to build it. But before the developer starts, look at the best way to implement the plan without interrupting business. In this second paper in the "Requirements modeling" series, learn important steps to take a new architecture from the drawing board to the next level, which is building. This paper continues to use the example of WidgetCo, a business that has grown very quickly in a short amount of time. WidgetCo has a limited but very dedicated IT department consisting of a network and server group, a developer group, and a recently added help desk staff. The developer has been brought in to rebuild the architecture to handle growth and reliability.

Tags: Application Development

Future Proofing Your Enterprise Architecture 2008-04-23 JupiterMedia

In this paper, Enterprise Architecture (EA) has been promoted as essential for the longevity of IT investments. EA is based on sound principles, but its implementation must address not just current business, but also how it will change in the future. If the points of change are planned for, then a future-proof IT infrastructure becomes reality. This paper looks at the key drivers of change, and how enterprise architectures can be used to address these drivers. Change in today's IT landscape is driven by three key kinds of factors: business, technological, and environmental.

Tags: Enterprise Architecture

Development Requirements Road Map: It's the Planning That Counts 2008-04-22 IBM

Shorten timelines, lower implementation costs, improve deliverable quality, and foster best practices by creating a logical road map that provides a framework for development project decision making. Advances in technology and software development have yielded powerful productivity tools intended to help shape a better future. However, without a well-planned blueprint to define the scope and business rules, prospects for a successful project are dim. After all, even the most ingenious and elegant code will be abandoned if it fails to deliver on key business goals in a timely and cost-effective manner. Indeed, even successful projects eventually hit their sunset as improvements become viable.

Tags: Application Development

Adopting Agile Development, Part 2: Understanding the Different Facets 2008-04-22 IBM

Part 1 of the agile development series introduced agile processes, the benefits of using them, and the requirements placed on the organization that uses them. This paper discusses how different types of organizations, such as start-ups, product companies, and small and large organizations, adapt to agile development. One will also learn how culture and pricing affect the process and outcomes.

Documenting Software Architecture, Part 1: What Software Architecture Is, and Why It's Important to Document It 2008-04-15 IBM

Software architecture has increasingly become important for the development of complex real-time systems. In this new series, learn why and how one should document software architecture. One will learn about the five different views, or aspects, that one should document for any medium-to large-scale software development project. This first paper in the series introduces software architecture and the importance of documentation. One will also get an overview of the architecture views that will be covered in upcoming papers.

Jump to [1] 2 3 4 5 6 7 8 9 10

Title	Date Added	Company
Optimizing Agile for Your Organization	2008-09-02	Construx Software Builders
Many organizations are interested in becoming Agile but wonder where to start. They want to ensure that their Agile adoption will achieve the desired benefits, goals, and objectives. This white paper outlines the major organization, cultural, and project considerations that are critical to a successful Agile adoption. It provides a starting point that works for most projects and organizations. Tags: Software Project Management, Methodology, Services, Application Development
Momentum Webcast: Can Process Improvement and Application Lifecycle Management Really Improve Your Business? (Level 100)	2008-06-25	Microsoft
The term Application Lifecycle Management (ALM) is attracting significant attention from tool vendors, research groups, and industry thought leaders. Although proactively managing the application throughout the life cycle seems to be a simple concept, in fact there are seemingly innumerable ways to accomplish the goals of ALM. Coordinated toolsets, the Capability Maturity Model, innovative modeling techniques, and commercially available processes all provide pieces of this frequently misunderstood and often complex puzzle. This webcast discusses the basic tenets of Application Lifecycle Management, describe what kinds of projects benefit most from ALM, explain how the Microsoft Visual Studio Team System supports this initiative, and examine why a repeatable, pragmatic software development process cannot be overlooked when implementing ALM. Tags: Application Development
The Software Development Life Cycle for Web 2.0: Realize the Benefits of Agile Development	2008-05-27	IBM
Any software development life cycle must be properly organized before the developer can expect to successfully execute a project. This is also true of Web 2.0, where a well-planned life cycle will let the developer realize the vision of building Web services in shorter development cycles, allow quick testing and deployment, and provide for service versioning. In this paper, get to know the software development life cycle for Web 2.0-based applications. Web 2.0 application-development processes need to be more agile than standard development methodologies allow for. In a Web 2.0 world, the users are going to be more agile in their thinking, will want things more quickly, and are getting used to rapid change. The role of Web 2.0-enabled content-management tools is becoming clear. Tags: Web Services, Application Development
Adopting Agile Development, Part 3: The Role of Agile Stakeholders	2008-05-20	IBM
Part 1 of this series introduced agile processes, the benefits of using them, and the requirements placed on the organization that uses them. Part 2 discusses how different types of organizations, such as start-ups, product companies, and small and large organizations, adapt to agile development. This paper discusses the different types of stakeholders in an agile process and what their roles entail. Stakeholders in the Srum process are highlighted. In software development, a stakeholder is a party who affects, or can be affected by, an organization's actions. The stakeholders are the entities within or outside of an organization that sponsor a project, have an interest in it, or stand to gain from the results of the project. Tags: Application Development
Documenting Software Architecture, Part 2: Develop the System Context	2008-05-13	IBM
Part 1 of this series explained the importance of a disciplined approach to documenting software architecture. It also introduced commonly used mechanisms to capture the architectural artifacts used in a typical software development process. This paper continues the discussion and focuses on the first important architecture artifact: the system context. Learn how to document the system context information with diagrams and information flows. Tags: Application Development
Requirements Modeling, Part 2: Build Your New Design	2008-04-29	IBM
After the developer has designed a new architecture, he is eager to build it. But before the developer starts, look at the best way to implement the plan without interrupting business. In this second paper in the "Requirements modeling" series, learn important steps to take a new architecture from the drawing board to the next level, which is building. This paper continues to use the example of WidgetCo, a business that has grown very quickly in a short amount of time. WidgetCo has a limited but very dedicated IT department consisting of a network and server group, a developer group, and a recently added help desk staff. The developer has been brought in to rebuild the architecture to handle growth and reliability. Tags: Application Development
Future Proofing Your Enterprise Architecture	2008-04-23	JupiterMedia
In this paper, Enterprise Architecture (EA) has been promoted as essential for the longevity of IT investments. EA is based on sound principles, but its implementation must address not just current business, but also how it will change in the future. If the points of change are planned for, then a future-proof IT infrastructure becomes reality. This paper looks at the key drivers of change, and how enterprise architectures can be used to address these drivers. Change in today's IT landscape is driven by three key kinds of factors: business, technological, and environmental. Tags: Enterprise Architecture
Development Requirements Road Map: It's the Planning That Counts	2008-04-22	IBM
Shorten timelines, lower implementation costs, improve deliverable quality, and foster best practices by creating a logical road map that provides a framework for development project decision making. Advances in technology and software development have yielded powerful productivity tools intended to help shape a better future. However, without a well-planned blueprint to define the scope and business rules, prospects for a successful project are dim. After all, even the most ingenious and elegant code will be abandoned if it fails to deliver on key business goals in a timely and cost-effective manner. Indeed, even successful projects eventually hit their sunset as improvements become viable. Tags: Application Development
Adopting Agile Development, Part 2: Understanding the Different Facets	2008-04-22	IBM
Part 1 of the agile development series introduced agile processes, the benefits of using them, and the requirements placed on the organization that uses them. This paper discusses how different types of organizations, such as start-ups, product companies, and small and large organizations, adapt to agile development. One will also learn how culture and pricing affect the process and outcomes.
Documenting Software Architecture, Part 1: What Software Architecture Is, and Why It's Important to Document It	2008-04-15	IBM
Software architecture has increasingly become important for the development of complex real-time systems. In this new series, learn why and how one should document software architecture. One will learn about the five different views, or aspects, that one should document for any medium-to large-scale software development project. This first paper in the series introduces software architecture and the importance of documentation. One will also get an overview of the architecture views that will be covered in upcoming papers.