SlideShare a Scribd company logo
ISD
      ERP
ESD
Technically                                       internal
specialized                         external                     Different
                                                                background
              rewards

discuss


                        No direct
Team                    customer
                         contact
                                                  groups




                                                                               Direct
                                                                             customer
                                                    consensus                 contact


                                What we do…..   How we do…..
Separation from the user (no users involved)
User’s concerns filtered by intermediaries
Product-oriented view
Entrepreneurial



Process called for user involvement at key
stages
Use of joint-application design(JAD)
techniques
Extensive interim documentation
Bureaucratic
• Experimental and Evolutionary Prototyping
   – Prototype presented by developers vs. expectations of the end
     customer testing group
• Agile Systems Development
   – High degree of creative conflict possible due to strong customer
     involvement e.g. DSDM
• Computer-Aided Software Engineering (CASE)
   – Because of mostly automated process there is less room for creative
     conflict
• Component Based Development (CBD)
   – Some potential for creative conflict because components have to fit to
     the overall goal
     But: Standardized components can be used and are predictable from
     the start
Enterprise Systems Development
package software employees are set up as a team but usually work
independently. Custom software employees are usually individual
workers but in fact they often work as a team.

  Reasons for the paradox:
  For package software time and goal are
  predefined. Because of that package
  software developers don’t have to align
  all the time and try to achieve the overall
  goal on time. Custom software
  employees got individual ideas and
  goals. To achieve a stable and usable
  product they have to align to create a
  common product with individual
  features.
Enterprise Systems Development
Enterprise Systems Development
Trend in recent years …..
    …. open source software
    Specialized
C
o
m
p
a
n
y

       General
                  package                     custom
                            S o f t w a r e
Qualitative Research




             Critic:
             Small group of observed companies
             treated as general business environment
             The ration of the research period was not
             distributed. No equal research period
             Generalizing assumptions that can’t be
             drawn upon this research (e.g. all package
             software companies employ PHD holders)

More Related Content

PPT
Best practices in enterprise applications
PDF
Approaching ATDD/BDD
PDF
Php Egypt Jan14
PDF
Writing Good Use Cases
PPT
How to write use cases
PDF
Software Engineering Large Practical coursework
PPTX
Building systems from off the shelf components
PPTX
Model-Based Systems Requirements
Best practices in enterprise applications
Approaching ATDD/BDD
Php Egypt Jan14
Writing Good Use Cases
How to write use cases
Software Engineering Large Practical coursework
Building systems from off the shelf components
Model-Based Systems Requirements

What's hot (16)

DOCX
Mi0033 – software engineering
PDF
Test Case, Use Case and Test Scenario
DOCX
Mit104 software engineering
PPTX
Object oriented analysis &design - requirement analysis
PPT
Prvt file test
PDF
Check upload1
DOCX
Mi0033 – software engineering
PDF
Unit 3- requirements for software development
DOCX
Testing overview
PPT
Black Box Testing
PDF
Test cases
DOCX
Updated_Mahesh Kumar_Software Engineer_3.6 Yr_Exp_in (Manual Automation and D...
PPT
Testing software security
PPTX
Unit testing
PPTX
Effective fault handling in SOA Suite 11g
Mi0033 – software engineering
Test Case, Use Case and Test Scenario
Mit104 software engineering
Object oriented analysis &design - requirement analysis
Prvt file test
Check upload1
Mi0033 – software engineering
Unit 3- requirements for software development
Testing overview
Black Box Testing
Test cases
Updated_Mahesh Kumar_Software Engineer_3.6 Yr_Exp_in (Manual Automation and D...
Testing software security
Unit testing
Effective fault handling in SOA Suite 11g
Ad

Similar to Enterprise Systems Development (20)

PPTX
My talk at PMI Sweden Congress 2013 on Agile and Large Software Products
PPT
Online Tv Music Channel Presentation
PDF
Agile Requirements by Agile Analysts
PDF
Configuration management
PDF
What next in the agile world - Alan Shalloway
PDF
Product Owners, Santa and other Goblins
PDF
Agility With Care: Managing Requirements Change with Agility In A Regulated P...
PDF
System Development
PDF
PD73002 Customer Needs
PPTX
How to Gather Requirements
PDF
Value Stream Manager concept applied to Software Product Development
PDF
Scr Position Paper For Chi 04 Workshop
PDF
Customer Centred Design in Financial Services
PDF
SAMPLE PROCESS - TEMPLATE
PDF
[StepTalks2011] Agility @ Scale - Rien Schot
PDF
Tdwi agile data warehouse - dv, what is the buzz about
PDF
Agile Prod Mgmt v. Proj Mgmt
PDF
1 jazz overview-karthik_k
 
PDF
Jazz Overview- Karthik K
PDF
Unosat19 April09
My talk at PMI Sweden Congress 2013 on Agile and Large Software Products
Online Tv Music Channel Presentation
Agile Requirements by Agile Analysts
Configuration management
What next in the agile world - Alan Shalloway
Product Owners, Santa and other Goblins
Agility With Care: Managing Requirements Change with Agility In A Regulated P...
System Development
PD73002 Customer Needs
How to Gather Requirements
Value Stream Manager concept applied to Software Product Development
Scr Position Paper For Chi 04 Workshop
Customer Centred Design in Financial Services
SAMPLE PROCESS - TEMPLATE
[StepTalks2011] Agility @ Scale - Rien Schot
Tdwi agile data warehouse - dv, what is the buzz about
Agile Prod Mgmt v. Proj Mgmt
1 jazz overview-karthik_k
 
Jazz Overview- Karthik K
Unosat19 April09
Ad

Enterprise Systems Development

  • 1. ISD ERP ESD
  • 2. Technically internal specialized external Different background rewards discuss No direct Team customer contact groups Direct customer consensus contact What we do….. How we do…..
  • 3. Separation from the user (no users involved) User’s concerns filtered by intermediaries Product-oriented view Entrepreneurial Process called for user involvement at key stages Use of joint-application design(JAD) techniques Extensive interim documentation Bureaucratic
  • 4. • Experimental and Evolutionary Prototyping – Prototype presented by developers vs. expectations of the end customer testing group • Agile Systems Development – High degree of creative conflict possible due to strong customer involvement e.g. DSDM • Computer-Aided Software Engineering (CASE) – Because of mostly automated process there is less room for creative conflict • Component Based Development (CBD) – Some potential for creative conflict because components have to fit to the overall goal But: Standardized components can be used and are predictable from the start
  • 6. package software employees are set up as a team but usually work independently. Custom software employees are usually individual workers but in fact they often work as a team. Reasons for the paradox: For package software time and goal are predefined. Because of that package software developers don’t have to align all the time and try to achieve the overall goal on time. Custom software employees got individual ideas and goals. To achieve a stable and usable product they have to align to create a common product with individual features.
  • 9. Trend in recent years ….. …. open source software Specialized C o m p a n y General package custom S o f t w a r e
  • 10. Qualitative Research Critic: Small group of observed companies treated as general business environment The ration of the research period was not distributed. No equal research period Generalizing assumptions that can’t be drawn upon this research (e.g. all package software companies employ PHD holders)