Databases
StackOverflow2013
Postsdbo
POUnstructured and not-documented software with bugs and problems
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnstructured and not-documented software with bugs and problems
    primarykey
    data
    text
    <p>Some time ago I started to develop an application. I had to learn how to do it, so I started with testing pieces of code, modules and libraries. From this testing stage I assembled many pieces that worked okay until the application did almost what it needed to do. However, very often I ran into exceptions, bugs, trouble, memory issues etc. To fix things I had the feeling I needed some sort of overall structure in the application to manage modules and so. I thought about using existing frameworks or design patterns. Unfortunately, at this stage I needed to quit the project. Nothing then was really documented and things only worked under very specific conditions. </p> <p>In the mean time conditions have changed and my memory started to fade a little. The application doesn't work and I'm not sure with modules I still use and which ones were meant for testing. Now there is a new need to finish the application in the <strong>least amount of time</strong> as possible. </p> <p>What is the best way to finish this? Which experiences do you have with this?</p> <p>To be honest, I only see one clear solution:</p> <p>I can start to reverse engineer the whole application; create UML specifications and other functional en technical design documentation. Afterwards I can split up the application into separate modules, redesign pieces, intensively unit-test them and combine all things together again. </p> <p>The main disadvantage: this takes <strong>a lot of time</strong>, maybe more than I spent on the app initially.</p> <p>Can you give me tips, learn me lessons or anything that might help to end this project fast. </p> <p>Maybe you have also tips to <strong>improve my performance</strong> in specifiying the designs, building the app and testing them.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UShsmit
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUnstructured and not-documented software with bugs and problems
      1. UShsmit
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload