1 / 17

Project activities and experiences in an Albanian software company

Project activities and experiences in an Albanian software company. Luan Jubica. Zagreb 2004. Objectives. Overview of the first experiences Problems New experiences. First experiences. It all began with 3-4 programmers wishing to build and accounting software

lmax
Télécharger la présentation

Project activities and experiences in an Albanian software company

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project activities and experiences in an Albanian software company Luan Jubica Zagreb2004

  2. Objectives • Overview of the first experiences • Problems • New experiences

  3. First experiences • It all began with 3-4 programmers wishing to build and accounting software • Continues with 2-3 “analysts” in our case accountants • The accountants where the “analysts” and the “testers” of the software • The programmers where the “designers” and “implementers”

  4. Programmers Accountants First experiences (cont...) Design AnalysisandDefinition Implementation Test

  5. First experiences (cont...) • Changes or modifications made by two persons • One programmer ( to do the implementation ) • One accountant ( to describe and test it ) • The programmer usually kept track of the changes and was responsible for versions of a certain software

  6. First experiences (sum up) • No real software process • Building only desktop applications • No project management or version control • No CASE tools used so far

  7. Environmental changes • Inside problems • Evolution in technology • Market changes

  8. What’s happening inside?! • Key members (developers) leaving the company. • The documentation of the products being very poor (limited to the code comments, or small documents). • Very difficult the tracking of versions.

  9. Evolution in technology • More advanced hardware features • New developing platforms • Database design facilities

  10. Market changes • Increasing computer usage and knowledge • Wider and more advanced technical equipment • Number of companies and their size growing • The company began to grow in terms of : • number of clients • requests for new software • The market required the software architecture to change in client/server.

  11. ! Immediate need for changes Problems (sum up) • More requirements • Quality • New features • More advanced security solutions • Leaking in management • No strategy • No versioning control • Members leaving

  12. New experiences • Technology • Management • The software process (some kind at least!!)

  13. Technology • Moved from Visual Basic 4 to Visual Basic 6.0 • Started using some CASE tools • Sybase Power Designer for database design • Microsoft Visio • Microsoft Visual Source Safe for version control • Code generation tools

  14. Management • The staff became organized in groups or teams (usually 3-4 team members) • Every team developed a new software or specific modules of existing ones • Started using CVS systems • Documenting changes using more sophisticated software (Microsoft Project)

  15. The software process • Started using a software process like RUP • Started using UML , building use cases • Rational Rose used as main CASE –tool in Analysis and Design phase

  16. Summary • Software process applied • New CASE tools • New project management • New code generation tools

  17. Thank you!

More Related