Download
software development techniques in albanian private software companies n.
Skip this Video
Loading SlideShow in 5 Seconds..
Software development techniques in Albanian private software companies PowerPoint Presentation
Download Presentation
Software development techniques in Albanian private software companies

Software development techniques in Albanian private software companies

251 Views Download Presentation
Download Presentation

Software development techniques in Albanian private software companies

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Arbora Dalaci, Esmeralda Kapcari borad_14@yahoo.com, esmeralda.kapcari@gmail.com 7th Workshop “Software Engineering Education and Reverse Engineering” Risan, Montenegro, 9 – 14 September 2007. Software development techniques in Albanian private software companies

  2. Software market in Albania • Actually in Albania there are 7 software development companies • About all these companies are partners (have purchased the licences) with: Oracle, Microsoft, IBM ... • Mostly they deal with private market but recently they are dealing with the government market too.

  3. Quality criteria of software products developed • Correctness – not so much • Reliability – not so much • Robustness – missing • Efficiency – not so much • User friendliness – good • Maintainability – ok; main profit for the company • Scalability – missing • Readability – poor • Reusability – ok • Modularity – ok • Portability – missing • Compatibility – ok • Testing – ok • Costs – main concern

  4. Quality criteria of software products developed

  5. The main phases from planning to the product • The representatives of the software development firm make a meeting with clients • Here are discussed the main requests about the product • There are not so many suggestions from the clients

  6. Analysis and definitions • It is made an analysis in cooperation with the client • Definitions keep on growing because it misses the methodology on the communication between the client and the solution provider. • Some times the lack of experience from the solution providers.

  7. The first meeting of the development group • Here are discussed the hardware platform were the product will be installed • The main technologies that will host and develop the software product. • During this meeting many questions about the product are raised and pointed out • At this point are defined the licenses needed to be purchased by the client

  8. The second meeting with the clients • Answers are given about the questions raised from the development group • Clients agree about the licenses and other technical conditions that are needed • Here it is agreed about the GUI; desktop or web application or both

  9. The second meeting of the development group • The project timeline (development, testing, implementation and maintenance) • Here are spotted the development phases and assignments • Here is done a cost estimation about the product

  10. The main modelling plan • Here mostly is used the spiral model as the development model for a software product. • Many meetings with the client during the development • Requests (by the client) may change during phases

  11. The development begins • During the development phases can be done several meeting with the representatives of the clients • Can be added or reformulated different specifications or requirements • The development is modular in most of the cases • During the module development there are done several testings on the modules

  12. Testing period • Gather together all the modules • A short period time of testing • At this period there are not spotted the logic problems but the errors that concern in the communications between the modules • After the testing period are revised the requirements for the product

  13. Implementation period • The installation of the software product • The configurations • The hardware installations • Some cases we concern with the connections testing to verify and achieve the technical requirements

  14. Product monitoring after implementation • Monitoring the performance • Monitoring of the reliability • Monitoring of the user friendliness • Monitoring of the security • Gathering of users feedback If any of these its not as was expected, the revision of the module is done.

  15. Maintanance • Depending on the type of contract • In-site or off-site maintenance • Can be as cost per call or fixed fee. • It is considered as the main source of profit for the software development company

  16. Thank You