不同的公司有不同的軟體開發程序，這樣的差異性是由於不同公司的產品、公司大小、人員不同所導致的，因此沒有通用於所有公司的標準軟體開發程序，各個公司需要訂定各自的軟體開發程序。

新創公司在幾個週期的軟體開發後，會產生公司文化，不同專案的軟體開發程序會受到這些公司文化影響而產生相似性，這表示不同專案的軟體開發程序擁有部份相同的開發程序，我們稱這些部份相同的開發程序為程序慣例，好的程序慣例可以降低軟體開發程序的差異性，因而提昇團隊的軟體品質。

新創公司是一種探索商業機會的小公司，他們以分散式程序以探索易變的市場需求，較少將軟體開發程序紀錄成文件，因此要在新創公司中找出需建立的程序慣例是困難的。

為了解決這個問題，我們提出了一個平台 - ProFrame，這個平台可以藉由微小文件整合來收集軟體開發程序，以降低將程序紀錄成文件的負擔，並提供一個分析模型來出程序慣例。

最後，我們在一個類似於新創公司的研究型實驗室進行了兩個案例研究，以探討該平台的有效性。結果顯示，該平台能夠有效地幫助新創公司從軟體開發程序中找出工具類、材料類的程序慣例。

Software processes vary significantly from one software company to another. The processes are different according to different product types, company size, and so on. It is impossible to build a “standard” software process that is applicable in all companies. Each company has to develop its unique process to fit in its own need.

After iterations of software development, disciplines are gradually formed in a software startup company (startup for short). The disciplines will be the practices for different projects in a startup similar. The similarity implies that there are common processes, called process routines, existing among for different projects. Good process routines can reduce software process variations in a growing startup, and therefore increase the software quality and team productivity.

Startups are usually small companies exploring new business opportunities. They use decentralized processes to deal with exploratory requirements in volatile market. The practices of software development are very few documented due to the decentralized processes and rapid change of requirement. Thus, the process routines are difficult to be discovered in startups.

To overcome this difficulty, a framework named ProFrame is proposed. The framework collects the practices by micro document integration. The micro documentation approach can reduce the burden of developers to document process practices. Further, ProFrame equips with an analysis model to discover process routines.

Two studies are presented to validate the effectiveness of ProFrame. The two studies were conducted based on simulated startup projects in DBSE research laboratory. The results show how ProFrame helps in discovering two process routines, the frequently used hidden tool chain and hidden supply chain, among simulated startup projects.

[1] S. Borzillo. Top Management Sponsorship to Guide Communities of Practice. Journal of Knowledge Management, 13(3):60--72, 2009.
[2] E. Carmel. Time-to-completion in software package startups. Proceedings of the Twenty-Seventh Hawaii International Conference on System Sciences, 4:498--507, Jan. 1994.
[3] J.-C. Derniame, B. A. Kaba, and D. G. Wastell. Software Process: Principles, Methodology, Technology. Springer-Verlag, 1999.
[4] S. Dorairaj, J. Noble, and G. Allan. Agile Software Development with Distributed Teams: Senior Management Support. IEEE 8th International Conference on Global Software Engineering, pages 197--205, Aug. 2013.
[5] H. Erdogmus. Essentials of Software Process. IEEE Software, 25(4):4--7, July 2008.
[6] M. Gholami, P. Jamshidi, and F. Shams. A Procedure for Extracting Software Development Process Patterns. Fourth UKSim European Symposium on Computer Modeling and Simulation (EMS), pages 75--83, Nov. 2010.
[7] C. Giardino, M. Unterkalmsteiner, N. Paternoster, T. Gorschek, and P. Abrahamsson. What Do We Know about Software Development in Startups? IEEE Software, 31(5):28--32, Sept. 2014.
[8] R. Glidden, C. Bockorick, S. Cooper, C. Diorio, D. Dressler, V. Gutnik, C. Hagen, D. Hara, T. Hass, T. Humes, J. Hyde, R. Oliver, O. Onen, A. Pesavento, K. Sundstrom, and M. Thomas. Design of Ultra-Low-Cost UHF RFID Tags for Supply Chain Applications. IEEE Communications Magazine, 42(8):140--151, Aug. 2004.
[9] T. Gorschek. Requirements Engineering Supporting Technical Product Management. Blekinge Tekniska Hogskola, 2006.
[10] P. Jarvinen. Research Questions Guiding Selection of an Appropriate Research Method . Proceedings of European Conference on Information Systems, pages 124--131, 2000.
[11] H. Jiau, C. H. Kao, K. C. Wu, and K.-F. Ssu. An Analysis Model for Software Project Development. IEEE International Conference on Management of Innovation and Technology, 2:673--677, June 2006.
[12] B. Kitchenham, L. Pickard, and S. L. Pfleeger. Case Studies for Method and Tool Evaluation. IEEE Software, 12(4):52--62, July 1995.
[13] J. Larkin and S. Herbert. Why a Diagram is (Sometimes) Worth Ten Thousand Words. Cognitive Science, 11(1):65 -- 100, 1987.
[14] A. H. M. Nurminen and A. Karkkainen. ProcMiner: Advancing Process Analysis and Management. IEEE International Conference on Data Engineering Workshop, pages 760--769, 2007.
[15] S. McBride and A. Paret. Cost Estimating in the Department of Defense and Areas for Improvement. Monterey, California. Naval Postgraduate School, 2010.
[16] M. Mendonca and V. Basili. Validation of an approach for improving existing measurement frameworks. IEEE Transactions on Software Engineering, 26(6):484 -- 499, 2000.
[17] N. Paternoster, C. Giardino, M. Unterkalmsteiner, T. Gorschek, and P. Abrahamsson. Software development in startup companies: A systematic mapping study. Information and Software Technology, 56(10):1200 -- 1218, 2014.
[18] M. Paulk, C. Weber, B. Curtis, and M. B. Chrissis. The Capability Maturity Model: Guidelines for Improving the Software Process. Addison-Wesley, 1995.
[19] E. Sadikov and M. Medina. Want a Tenure?: Try a Startup. The ACM Magazine for Students - The Role of Academia in the Startup World, 18(4):16--19, June 2012.
[20] C. Saratxaga, C. Alonso-Montes, O. Haugerr, C. Ekelirr, and A. Mitschke. Product Line Tool-Chain: Variability in Critical Systems. Product Line Approaches in Software Engineering (PLEASE), 2012 3rd International Workshop on, pages 57--60, June 2012.
[21] C. P. Team. CMMI for Development Version 1.3. Software Engineering Institute, 2010.
[22] E. P. Team. Company Startup Stages.
[23] K. P. Team. Kivy 1.9.0-dev documentation. 2014.
[24] O. Turetken and O. Demirors. An Approach for Decentralized Process Modeling. Proceedings of the International Conference on Software Process, pages 195--207, 2007.
[25] W. van der Aalst, T. Weijters, and L. Maruster. Workflow Mining: Discovering Process Models from Event Logs. IEEE Transactions on Knowledge and Data Engineering, 16(9):1128--1142, Sept. 2004.
[26] G. van der Veer and M. van Welie. Task Based Groupware Design: Putting Theory into Practice. Proceedings of the Third Conference on Designing Interactive Systems: Processes, Practices, Methods, and Techniques, pages 326-
-337, 2000.
[27] T. Yokoi and H. Yanagimoto. Topic Extraction for a Large Document Set with the Topic Integration. Proceedings of the Third International Conference on Knowledge Discovery and Data Mining, pages 46--49, 2010.
[28] M. V. Zelkowitz and D. R. Wallace. Experimental Models for Validating Technology. IEEE Computer, 31(5):23--31, May 1998.