2011 TGMC
0 likes228 views
This certificate recognizes LUBHNA KAUL from GRAPHIC ERA INSTITUTE OF TECHNOLOGY for participating as a member of a team in IBM's annual National Software Development Program called "The Great Mind Challenge - 2011".
1 of 1
Download to read offline
Ad
Recommended
IBM TGMC Certificate
IBM TGMC CertificateDipin Kanojia
油
This certificate was awarded to Dipin Kanojia of Team theband from Institute Of Information Technology And Management for participating in the Annual National Software Development Program by IBM called "The Great Mind Challenge - 2009".IBM_Participation_4
IBM_Participation_4Jatinder Bhola
油
This certificate recognizes Satish Verma's participation as a member of Team Omniscient from CT Institute of Engineering Management and Technology in IBM's annual National Software Development Program called "The Great Mind Challenge - 2011".Innovate presentation
Innovate presentationKristin Cowhey
油
This document discusses changes in software development approaches from the past to present. It summarizes:
1) Development in the past was more process-driven, used proven technologies, required substantial financial investment, and produced relatively stable software. Now development uses agile methodologies, places more emphasis on traceability, and targets modern devices like Android and iPad.
2) Two IBM mainframe developers discuss bridging the gap between past and present approaches through use of IBM Rational software. Cultural and technological differences present challenges.
3) Training, mentoring, and performance support are key to successfully implementing new development solutions and managing organizational change. A learning-centered approach can help teams apply new skills and sustain productivity.component based development model
component based development modelMuneeba Qamar
油
Component-based software engineering (CBSE) involves building software using pre-existing software components rather than developing everything from scratch. Well-designed components interact through defined interfaces, are modular, deployable, and replaceable. CBSE allows for increased reliability, reduced risks, effective specialist use, and accelerated development by reusing tested components instead of recreating them. Potential disadvantages include increased initial development time and difficulty testing components for unknown uses.Improving software econimics
Improving software econimicsKalica Wadhwa
油
This document discusses improving software economics through a balanced approach of reducing application size and complexity, improving development processes, using skilled personnel, creating better environments, and focusing on quality. It focuses on reducing size, particularly through using higher-level programming languages, object-oriented methods and visual modeling, reuse, and commercial components. It also discusses improving software processes by making each step more efficient, eliminating unnecessary steps, and employing concurrency where possible.A cost model for software reuse
A cost model for software reuseasas402
油
This document discusses applying cost modeling concepts like return on investment and payback period to software reuse. It outlines barriers to reuse like lack of quantifiable results and not invented here attitudes. The document also describes developing a reuse strategy through an enterprise program that sources artifacts from component development, project teams, and application development to maximize return on investment.Component Based Software Development
Component Based Software DevelopmentDiego Cardozo
油
This document discusses component-based software development (CBSD). It defines a software component and lists its criteria. CBSD allows for higher reuse, simplifies testing and maintenance, and leads to better quality and shorter development cycles compared to traditional software engineering. Example applications of CBSD include COM and CORBA. Content management systems (CMS) are also discussed as they are fundamentally based on CBSD principles, treating pages, images, and other elements as components. WebMatrix and OrchardCMS are presented as tools that facilitate CBSD.Software component reuse repository
Software component reuse repositorySandeep Singh
油
This document discusses software reuse and component-based development. It defines software reuse as creating software from existing software components rather than building from scratch. Component-based development allows large, abstract enterprise components to be reused to reduce development time. There are different types of software reuse and several benefits including increased reliability, reduced risks, and accelerated development. Component retrieval is discussed as an important part of software reuse, but it remains a difficult problem to find efficient solutions. Overall, the document presents an overview of software reuse and component-based development while noting that more work is still needed to improve component retrieval methods.Component based-software-engineering
Component based-software-engineeringWasim Raza
油
After studying this presentation you will be able to learn component based software engineering,what are components,what are advantageous,what are components,what are COTS.How to start doing ci
How to start doing ciFazreil Amreen Abdul Jalil
油
This document discusses continuous integration (CI), describing it as a practice of frequent integration of code changes into a shared repository. It outlines how CI can be implemented through defining a build strategy, selecting appropriate tools, and extending CI features. The document also shares experiences applying CI using top-down and bottom-up approaches and how CI setup can be standardized or adaptive based on project needs. It notes the benefits of CI include transparent changes, real-time integration, automation, and empowering education while also emphasizing the importance of tool selection, team discipline, delivering quality code, and having a shared vision.CS6201 Software Reuse - Design Patterns
CS6201 Software Reuse - Design PatternsKwangshin Oh
油
This document discusses design patterns, including their origin in architecture, history in software design, description formats, different types of patterns like architectural patterns, pattern catalogs, and pattern systems. It provides an example of the singleton pattern and discusses some drawbacks of patterns.Component Base Development
Component Base DevelopmentFrik khechoomian
油
This document discusses component-based development. It presents on software reuse, separation of concerns, and component-based software engineering. The key aspects covered are defining, implementing, verifying, validating and delivering components. Classification and retrieval of components from a library is also addressed.Presentation on component based software engineering(cbse)
Presentation on component based software engineering(cbse)Chandan Thakur
油
The document presents an overview of component based software engineering. It discusses what a component is, the fundamental principles of CBSE, the CBSE development lifecycle, and metrics used in CBSE. Benefits include reduced complexity and development time while difficulties include quality of components and satisfying requirements. CBSE uses pre-built components while traditional SE builds from scratch. Current component technologies discussed are CORBA, COM, EJB, and IDL. Applications of CBSE are in many domains.Reusability
Reusabilityuniversity of education,Lahore
油
1. The document discusses reusability in object-oriented analysis and design and software engineering. It states that reusability is promoted through frameworks that encourage reusing existing software components rather than redeveloping them.
2. Software engineers practice reusability through reusing expertise, standard designs and algorithms, libraries of classes and procedures, frameworks, and complete applications. Frameworks provide common, reusable facilities for different application programs to build upon.
3. Examples of frameworks discussed are ones for payroll management and e-commerce websites, which could implement common features for different businesses to customize for their individual needs, saving development time.Software resuse
Software resuseIndu Sharma Bhardwaj
油
The document discusses software reuse and component-based software engineering. It describes how reuse can happen at different levels from full application systems down to individual functions. Reusing code, specifications, and designs can improve reliability, reduce risks and costs, and speed up development time. However, reuse requires an organized component library, confidence in component quality, and documentation to support adaptation. The document also outlines processes for incorporating reuse into development and enhancing the reusability of components.Agile
Agileratem
油
This document discusses mapping agile methods to ERP development and identifies directions and limitations. It motivates using agile due to long delays and misfits with waterfall ERP development. Several agile principles like iterative development, ubiquitous language, test-driven development, and continuous integration are described. However, limitations include cultural barriers like predictive planning mindsets and technical barriers like legacy technologies. The conclusion calls for overcoming barriers and further research on agile technique adoption levels and behavior-driven development for ERP.What is a power point?
What is a power point?theseekingseaker
油
A power point is a Microsoft software that allows users to create interactive presentations. It can be used to make presentations for business, school, or personal use. Power point presentations allow users to share information visually through slides, images, and other multimedia elements.Ch18
Ch18phanleson
油
This document discusses different approaches to software reuse, including design patterns, application frameworks, component reuse, and generator-based reuse. It covers the benefits of reuse, such as increased dependability and accelerated development, as well as potential problems like increased maintenance costs and the "not invented here" syndrome. Design patterns and generator-based reuse are highlighted as approaches that allow for concept reuse through reusable abstractions rather than just code or component reuse. The Observer design pattern is presented as a specific example.Software Reuse: Challenges and Business Success
Software Reuse: Challenges and Business SuccessUniversity of Zurich
油
The document discusses challenges and business success related to software reuse. It outlines topics like reuse challenges, technologies, economics, case studies and empirical investigations. Regarding challenges, it notes organizational, technical, domain engineering, and economic aspects. For technologies, it discusses software analysis/visualization, product lines, and architectures. It also examines cost/benefit relationships, metrics, and legal issues regarding reuse. Case studies from HP and Ericsson demonstrate quality, productivity and economic benefits of large-scale reuse programs. Strategies for successful reuse include formal reuse programs with quality control and continuous improvement.Designing Delivery: Rethinking IT in the Digital Service Economy - Jeff Sussna
Designing Delivery: Rethinking IT in the Digital Service Economy - Jeff SussnaAndr辿s Felipe Cano Sierra
油
1) Traditional large-scale IT projects often failed because project plans did not accurately predict challenges, requirements did not model real user needs, and user needs changed over long implementation periods.
2) IT traditionally took an industrial approach to building and operating systems with high upfront costs and presumed returns, developing systems in linear phases from conception to completion.
3) The DevOps approach aims to break down barriers between development and operations so that software functionality and operability are inseparable, improving speed and reducing misunderstandings compared to separate development and operations teams.Ad
More Related Content
What's hot (12)
Component based-software-engineering
Component based-software-engineeringWasim Raza
油
After studying this presentation you will be able to learn component based software engineering,what are components,what are advantageous,what are components,what are COTS.How to start doing ci
How to start doing ciFazreil Amreen Abdul Jalil
油
This document discusses continuous integration (CI), describing it as a practice of frequent integration of code changes into a shared repository. It outlines how CI can be implemented through defining a build strategy, selecting appropriate tools, and extending CI features. The document also shares experiences applying CI using top-down and bottom-up approaches and how CI setup can be standardized or adaptive based on project needs. It notes the benefits of CI include transparent changes, real-time integration, automation, and empowering education while also emphasizing the importance of tool selection, team discipline, delivering quality code, and having a shared vision.CS6201 Software Reuse - Design Patterns
CS6201 Software Reuse - Design PatternsKwangshin Oh
油
This document discusses design patterns, including their origin in architecture, history in software design, description formats, different types of patterns like architectural patterns, pattern catalogs, and pattern systems. It provides an example of the singleton pattern and discusses some drawbacks of patterns.Component Base Development
Component Base DevelopmentFrik khechoomian
油
This document discusses component-based development. It presents on software reuse, separation of concerns, and component-based software engineering. The key aspects covered are defining, implementing, verifying, validating and delivering components. Classification and retrieval of components from a library is also addressed.Presentation on component based software engineering(cbse)
Presentation on component based software engineering(cbse)Chandan Thakur
油
The document presents an overview of component based software engineering. It discusses what a component is, the fundamental principles of CBSE, the CBSE development lifecycle, and metrics used in CBSE. Benefits include reduced complexity and development time while difficulties include quality of components and satisfying requirements. CBSE uses pre-built components while traditional SE builds from scratch. Current component technologies discussed are CORBA, COM, EJB, and IDL. Applications of CBSE are in many domains.Reusability
Reusabilityuniversity of education,Lahore
油
1. The document discusses reusability in object-oriented analysis and design and software engineering. It states that reusability is promoted through frameworks that encourage reusing existing software components rather than redeveloping them.
2. Software engineers practice reusability through reusing expertise, standard designs and algorithms, libraries of classes and procedures, frameworks, and complete applications. Frameworks provide common, reusable facilities for different application programs to build upon.
3. Examples of frameworks discussed are ones for payroll management and e-commerce websites, which could implement common features for different businesses to customize for their individual needs, saving development time.Software resuse
Software resuseIndu Sharma Bhardwaj
油
The document discusses software reuse and component-based software engineering. It describes how reuse can happen at different levels from full application systems down to individual functions. Reusing code, specifications, and designs can improve reliability, reduce risks and costs, and speed up development time. However, reuse requires an organized component library, confidence in component quality, and documentation to support adaptation. The document also outlines processes for incorporating reuse into development and enhancing the reusability of components.Agile
Agileratem
油
This document discusses mapping agile methods to ERP development and identifies directions and limitations. It motivates using agile due to long delays and misfits with waterfall ERP development. Several agile principles like iterative development, ubiquitous language, test-driven development, and continuous integration are described. However, limitations include cultural barriers like predictive planning mindsets and technical barriers like legacy technologies. The conclusion calls for overcoming barriers and further research on agile technique adoption levels and behavior-driven development for ERP.What is a power point?
What is a power point?theseekingseaker
油
A power point is a Microsoft software that allows users to create interactive presentations. It can be used to make presentations for business, school, or personal use. Power point presentations allow users to share information visually through slides, images, and other multimedia elements.Ch18
Ch18phanleson
油
This document discusses different approaches to software reuse, including design patterns, application frameworks, component reuse, and generator-based reuse. It covers the benefits of reuse, such as increased dependability and accelerated development, as well as potential problems like increased maintenance costs and the "not invented here" syndrome. Design patterns and generator-based reuse are highlighted as approaches that allow for concept reuse through reusable abstractions rather than just code or component reuse. The Observer design pattern is presented as a specific example.Software Reuse: Challenges and Business Success
Software Reuse: Challenges and Business SuccessUniversity of Zurich
油
The document discusses challenges and business success related to software reuse. It outlines topics like reuse challenges, technologies, economics, case studies and empirical investigations. Regarding challenges, it notes organizational, technical, domain engineering, and economic aspects. For technologies, it discusses software analysis/visualization, product lines, and architectures. It also examines cost/benefit relationships, metrics, and legal issues regarding reuse. Case studies from HP and Ericsson demonstrate quality, productivity and economic benefits of large-scale reuse programs. Strategies for successful reuse include formal reuse programs with quality control and continuous improvement.Designing Delivery: Rethinking IT in the Digital Service Economy - Jeff Sussna
Designing Delivery: Rethinking IT in the Digital Service Economy - Jeff SussnaAndr辿s Felipe Cano Sierra
油
1) Traditional large-scale IT projects often failed because project plans did not accurately predict challenges, requirements did not model real user needs, and user needs changed over long implementation periods.
2) IT traditionally took an industrial approach to building and operating systems with high upfront costs and presumed returns, developing systems in linear phases from conception to completion.
3) The DevOps approach aims to break down barriers between development and operations so that software functionality and operability are inseparable, improving speed and reducing misunderstandings compared to separate development and operations teams.Designing Delivery: Rethinking IT in the Digital Service Economy - Jeff Sussna
Designing Delivery: Rethinking IT in the Digital Service Economy - Jeff SussnaAndr辿s Felipe Cano Sierra
油
2011 TGMC
- 1. Certificate of Participation This certificate has been awarded to Member of Team from for participating in Annual National Software Development Program by IBM LUBHNA KAUL MASTER'S GRAPHIC ERA INSTITUTE OF TECHNOLOGY The Great Mind Challenge - 2011